Re: Proposal: create meaningful aliases for git reset's hard/soft/mixed
- From
- Philippe Vaucher <philippe.vaucher@gmail.com>
- Date
- Dec 2, 2011, 14:27 UTC
- Message-ID
- <CAGK7Mr7zdstbm7QsrYq9a6m9ui_r8Ak8XtyWADLQ0n-mXiov4w@mail.gmail.com>
- In-Reply-To
- <CABURp0rtCUbJXLHtXv_1g6GRKL3mX-T+3vN1=QO4CUibqXdEMg@mail.gmail.com>
> > Why worse? I'd understand if you said it's doesn't improve it enough > > for it to be worth the change tho. > > I think that's what "you should aim higher" means.
Yes, but my question was why was the proposal _worse_ in his mind. Anyway, it's not really important, probably something he typed in a hurry.
> How about: > --soft: git checkout -B <commit> > --mixed: git reset -- <paths> > --hard: git checkout --clean
I like the idea... but as other pointed out those are not equivalent.
Maybe we'd start by listing the features we want to be able to do:
- Move git's HEAD to a particular commit without touching the files or the index - Move git's HEAD to a particular commit and clear the index but without touching the files - Move git's HEAD to a particular commit and clear the index and have all the files match that particular commit files - Move git's HEAD to a particular commit and clear the index and have all the files match that particular commit files and remove files that are unknown to that commit
Is there a scenario I'm missing? Once we have the scenarios nailed down we can start thinking about how to express them.
Philippe