From: "George Spelvin" <linux@horizon.com>
To: gitster@pobox.com, linux@horizon.com
Cc: git@vger.kernel.org, jacob.keller@gmail.com, tytso@mit.edu
Subject: Re: Why not git reset --hard <path>?
Date: 28 Sep 2015 19:52:09 -0400 [thread overview]
Message-ID: <20150928235209.29725.qmail@ns.horizon.com> (raw)
In-Reply-To: <xmqqr3lib189.fsf@gitster.mtv.corp.google.com>
Junio C Hamano <gitster@pobox.com> wrote:
> "George Spelvin" <linux@horizon.com> writes:
>> "git checkout <tree-ish> <pathspec>" modifies the index?
>>
>> Damn, I've been using git for years and I never knew that.
>
> ... which would be an indication that the behaviour is most likely
> the most natural one.
I think it's more that often, staging a file to the index
is pretty harmless, so it doesn't actually matter.
Both of the commonest forms of commit ("git commit -a" and "git commit
[-o] <paths>") aren't affected, and if I'm doing something trickier,
I'll usually examine the status and make sure I've got it right.
So I could have encountered it and put it down to fat-fingering on
my part.
>> But I just tested, and it does. Damn, now I have to figure out
>> how to "leapfrog" a file from history into the working tree without
>> overwriting the index; that's occasionally useful.
> ... and indeed it is useful in some rare cases. Either
>
> git diff <tree-ish> <pathspec> | git apply -R
>
> or
>
> git checkout <tree-ish> <pathspec> &&
> git reset <pathspec>
The former would work, and thanks for the idea, but for a single file
I'd probably do one of
git show <tree-ish>:<path> > <path>
git cat-file blob <tree-ish>:<path> > <path>
The checkout/reset wouldn't work in the case I'm thinking about, which
is when I want to import a small piece (say, helper function that got
deleted) from an old or other-branch version of a file. I.e. a partial
revert or cherry-pick.
If I had some current changes to merge with, I'd stage them, pull the
*other* version into the tree, and use something like git-gui to add the
hunk I want to the staged version.
The whole point is that the staged state is important and I don't
want it overwritten.
There are other ways, of course:
- Show or cat-file the other version into a temporary file and manually
copy and paste. No need to stage anything.
- Commit the current change, then add the additional changes and amend the
commit.
prev parent reply other threads:[~2015-09-28 23:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 20:34 Why not git reset --hard <path>? George Spelvin
2015-09-28 20:42 ` Junio C Hamano
2015-09-28 20:53 ` Jacob Keller
2015-09-28 21:19 ` Junio C Hamano
2015-09-28 21:36 ` Theodore Ts'o
2015-09-29 7:06 ` Jacob Keller
2015-09-29 16:15 ` George Spelvin
2015-09-29 19:40 ` Philip Oakley
2015-09-28 22:36 ` George Spelvin
2015-09-28 22:58 ` Junio C Hamano
2015-09-28 23:52 ` George Spelvin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150928235209.29725.qmail@ns.horizon.com \
--to=linux@horizon.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacob.keller@gmail.com \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).