Re:Purposes, Concepts, Misfits, and a Redesign of Git
by toomim on Friday September 30, 2016 @08:04PM
(#12615945)
You find it hard to create a list? Here's an example of making a staging file:
And committing the file:
[ Parent
| on HN ]
Re:Purposes, Concepts, Misfits, and a Redesign of Git
by jdmichal on Friday September 30, 2016 @11:25PM
(#12616404)
Congrats. You just recreated a bad implementation of the staging area in a text file.
Re:Purposes, Concepts, Misfits, and a Redesign of Git
by toomim on Saturday October 01, 2016 @01:38AM
(#12616642)
Congrats, you got the joke! ;)
A staging area is just a list of things to commit. There are many ways to make lists. I personally use emacs because direct manipulation rocks. Complaining about a change in one way to make lists is silly—gitless introduces much more powerful basic mechanisms like uncommitted branching, and lists belong on top of these more powerful basic features; not underneath like in the traditional porcelain.
Re:Purposes, Concepts, Misfits, and a Redesign of Git
by qznc on Saturday October 01, 2016 @05:41AM
(#12617202)
The staging area is finer than files. It is more like a diff, where you can change parts of a file.
For example, I usually use git-add -p to put my changes in staging without the debug print statements. I still want to keep them in my working copy.
Re:Purposes, Concepts, Misfits, and a Redesign of Git
by to3m on Friday September 30, 2016 @09:12PM
(#12616128)
Dude.
Re:Purposes, Concepts, Misfits, and a Redesign of Git
by AlexCoventry on Friday September 30, 2016 @11:27PM
(#12616407)
Is there a handy way to stage the current changes, then make further unstaged changes prior to the commit?