4 ms·
> As other people have pointed out, most new version control tools can do this without a staging area. Fair enough. > No it doesn't, and they explain how. Wit
by jogjayr 10y ago
> As other people have pointed out, most new version control tools can do this without a staging area.
Fair enough.
> No it doesn't, and they explain how. With combined branches + stashes, you'd do a checkout of a new branch from the commit before your stashed changes.
Ah, OK. However, I still maintain that I have other uses for stash that don't easily conform to git stash --all; git co new-branch.
I read the article (though it appears not closely enough). I will admit to not reading the original paper (until now), but I did skim gitless's documentation a few weeks back when it appeared on HN. Even then I was struck with a touch of "What is all this new s&%# I like how my git is right now stop messing with it"
Like I said, I'm willing to admit that because I already know all of git's sharp edges, gitless may simply not appeal to me. However, it's totally possible that gitless really does make git simpler for new users and it's the future of git.
- StavrosK 10y agoStashing gets done the way we did it in the bzr days: scm stash <filename> # Stash a whole file scm stash -p <filename> # Stash a part of a file scm stash -p # Stash parts of the whole project Works as well as a staging area (because it's just the complementary operation) without needing a staging area, and without all the cognitive burden. Saying "you can put changes aside for later" is much easier than explaining the different states of a file in the staging area.