News for hackers. Stuff that matters.
Re:Purposes, Concepts, Misfits, and a Redesign of Git by e12e on Sunday October 02, 2016 @08:22AM (#12622039)
> 2. As a simple "review" system. You stage files that have been reviewed so you know you don't have to look at them again, while continuing on a change.

(How) does this work if you want/need a virtual paper trail of reviews and/or in a distributed team? Do you email your changes for review, without making a commit and push (to a branch and/or fork)? Apologies if I misunderstand what you mean, but I read "review" here as colleague walks by and have a look, and says lgtm?

Re:Purposes, Concepts, Misfits, and a Redesign of Git by kcburge on Sunday October 02, 2016 @11:50AM (#12622863)
This is personal review, not peer review. I try to review my code after completion and a period of rest before submitting for peer review. This discipline finds a surprising number of issues with my code that I just didn't see when I was tired, sick of looking at the code, and just ready to be done with it. I stage the changes as I go (particularly the small changes) and leave the meaty changes for last to be analyzed carefully against the original source.