News for hackers. Stuff that matters.
Re:I'm going to slowly move on from Mercurial by JoshTriplett on Monday January 25, 2016 @03:48PM (#10969835)
> "I find [the index] a critical part of git's culture of making small commits with one logical change each."

> I've never understood why the index has to be forced on everyone for every commit.

You can generally bypass it if making a simple commit; I use "git commit -a" all the time. But every time you use tools like "git add" on individual files, or "git add -p" on parts of files, you rely on the index.

Understanding the index also helps greatly when you need to do a merge, cherry-pick, or other similar operation; you need a staging area to work in, separate from the work tree.

Re:I'm going to slowly move on from Mercurial by krupan on Monday January 25, 2016 @04:16PM (#10970001)
"Understanding the index also helps greatly when you need to do a merge, cherry-pick, or other similar operation; you need a staging area to work in, separate from the work tree."

Actually, with mercurial I don't need a staging area to work in separate from the working copy to perform merge, cherry-pick, or other similar operations. The index appears to be needless complication.

Re:I'm going to slowly move on from Mercurial by scrollaway on Monday January 25, 2016 @11:24PM (#10971807)
Having used both git and mercurial extensively I can guarantee you the index is not a needless complication, it is a feature sorely missed in hg.
Re:I'm going to slowly move on from Mercurial by jordigh on Tuesday January 26, 2016 @07:57AM (#10973158)
With `hg commit --interactive` and `hg amend --interactive`, I really don't see what's the difference between a temporary commit that you keep adding stuff to and a staging area. It's all just diffs and hunks. Whether it's finalised or not is just a matter of perspective. Mercurial encodes this perspective by distinguishing draft from published commits.