Re:Mercurial RFC of a new extension to directly operate on G...
by throw0101a on Wednesday October 30, 2019 @08:54AM
(#21397140)
> I don't believe hg has an equivalent of the git index, although there are other ways to get similar functionality if you want it.
Queues?
* http://stevelosh.com/blog/2010/08/a-git-users-guide-to-mercu...
Re:Mercurial RFC of a new extension to directly operate on G...
by MiyamotoAkira on Wednesday October 30, 2019 @06:59AM
(#21396327)
>> 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.
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.
For the most part, you can do anything with either one that you could do with the other, and the practical differences are mostly just in the UI, as well as a cultural component (e.g. hg more strongly discouraging history rewriting is part UI, part culture). Personally, I prefer the git UI because it has a more direct mapping onto manipulating a DAG of commits, but obviously not everyone feels that way, and I don't expect them to. When I first started with DVCS, I started with hg since it seemed easier to learn.
(Although really, my DVCS UI of choice is Magit, which I use for 99.9% of git stuff, to the point where I almost never need to actually run git myself on the command line.)