Timeline for What does 'stage' mean in git?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 29, 2020 at 17:49 | comment | added | Ron Burk | Were git being designed from scratch, this could have just been part of a generalized "branch" concept, local and unseen by others in this case. Likewise "stash" could have just been implemented (and understood!) as a specific instance of the generalized concept of "branch." You could then have any number of levels of "staging" you prefer. | |
| Aug 13, 2019 at 15:58 | comment | added | alelom | I found this answer to be immensely better than all the above, since it's the only one that clarifies why Staging exists at all (being technically required), an explanation of its origin (Git's authors chose to make this step visible and persistent), adding what I personally find to be a good definition for it (an intermediate, unnamed, uncommented local commit). However, I think it could be improved by quoting a source for the statement about the origin of Staging, and elaborate some more on why it's technically required. @OldPro | |
| Aug 27, 2018 at 14:27 | review | Suggested edits | |||
| Aug 27, 2018 at 21:07 | |||||
| Apr 29, 2014 at 21:18 | comment | added | Old Pro | @gnat yes, of course many other VCS give you something like staging. By "other VCS" I mean other VCS that don't have something like git's stage, since that is what the OP was referring to. | |
| Apr 29, 2014 at 20:39 | comment | added | gnat | "other VCS don't" -- what makes you think so? Shelving at Perforce appears to be doing what you describe, and even with few additional bells and whistles | |
| Apr 29, 2014 at 20:34 | history | answered | Old Pro | CC BY-SA 3.0 |