Re:Mercurial RFC of a new extension to directly operate on G...
by rcthompson on Wednesday October 30, 2019 @10:35AM
(#21398181)
I'm not sure I follow. A git history is literally a DAG of commits, and if you understand what each command is doing in terms of that DAG, there's very little abstraction at all, so there's nothing to leak.
That would be a leaky abstraction. The fact that is using DAG should be irrelevant. If they find a better way of doing the work, that shouldn't really affect the ux.