2 ms·
>> more direct mapping onto manipulating a DAG of commits That would be a leaky abstraction. The fact that is using DAG should be irrelevant. If they find a be
by MiyamotoAkira 7y ago
>> more direct mapping onto manipulating a DAG of commits
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.
- rcthompson 7y agoI'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.