Re: Git reset -p on working tree
- From
knittl <knittl89@googlemail.com>
- Date
- Nov 23, 2010, 10:58 UTC
- Message-ID
- <AANLkTi=5w3YpYu0_WbmHud0BUkO2BqYNVezWDMkCaSj2@mail.gmail.com>
- In-Reply-To
- <AANLkTindHnjeXEGbKWiQkWgoUBwqZbdx71sQwNr_gFp0@mail.gmail.com>
On Tue, Nov 23, 2010 at 11:32 AM, Jeenu V <jeenuv@gmail.com> wrote:
Show 18 quoted lines
> On Tue, Nov 23, 2010 at 3:56 PM, Jeenu V <jeenuv@gmail.com> wrote:
>> On Tue, Nov 23, 2010 at 2:50 PM, knittl <knittl89@googlemail.com> wrote:
>>>> Right now I do this with vimdiff, by applying 'git diff' in reverse.
>>>> Wish reset supports -p on working tree operations as well because the
>>>> -p framework (of add, and reset) feels good to use.
>>>
>>>
>>> there's `git checkout -p` to selectively remove changes from your working tree.
>>> (also `git stash -p` to selectively stash changes temporarily)
>>
>> Surprised to know that checkout and stash supports it! Thanks a lot
>> for pointing out.
>
> I think Git could suggest 'checkout -p' and/or 'stash -p' when user
> tries to use -p with --{hard,soft,mixed} with reset command (in
> addition to mentioning that they're incompatible), since relatively
> new users are used to 'reset' than other commands to reset their
> working trees.`git reset` seldomly affects the working tree, unless using `--hard`, `--merge` or `--keep`, and those switches are potentially dangerous if you are not aware of the implications to your worktree and index.
without options reset undoes a previous add, i.e. remove changes from the index, but not the working tree.
git reset manpage mentions git-checkout:
Show 5 quoted lines
> After running git reset <paths> to update the index entry, you can > use git-checkout(1) to check the contents out of the index to the > working tree. Alternatively, using git-checkout(1) and specifying a > commit, you can copy the contents of a path out of a commit to the > index and to the working tree in one go.
-- typed with http://neo-layout.org myFtPhp -- visit http://myftphp.sf.net -- v. 0.4.7 released!