From: Sitaram Chamarty <email@example.com>
To: Junio C Hamano <firstname.lastname@example.org>,
Piotr Krukowiecki <email@example.com>
Subject: Re: Checkout file without changing index?
Date: Thu, 25 Apr 2019 09:10:50 +0530 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 24/04/2019 19.16, Junio C Hamano wrote:
> Piotr Krukowiecki <email@example.com> writes:
>> I was familiar with "git checkout revision -- file".
>> But it updates both working tree and index. I had some changes in
>> index (staged) and "git checkout HEAD -- file" silently overwritten
>> it. Well, probably my mistake, it's documented.
> We'd invite you to live on the leading edge and try
> $ git restore --source=<revision> <pathspec>
> which by default checks things out only to the working tree, but not
> to the index (you say --staged if you want to restore to the index,
> and you say --worktree if you want to restore to the working tree,
> or you can say both, which would be the same as "git checkout").
> I think the new command is now on the 'pu' branch, but in a few
> weeks hopefully it will appear on the 'next' branch.
I'm not in a position to use either of those on at least some of my
systems, but meanwhile, I thought I'd ask this: what is the difference
between this and "git show REF:PATH > PATH", in terms of side-effects.
(I.e., any differences other than looking cleaner, not having to repeat
next prev parent reply other threads:[~2019-04-25 3:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 13:37 Checkout file without changing index? Piotr Krukowiecki
2019-04-24 13:46 ` Junio C Hamano
2019-04-24 18:15 ` Piotr Krukowiecki
2019-04-24 20:16 ` Philip Oakley
2019-04-25 3:40 ` Sitaram Chamarty [this message]
2019-04-25 4:02 ` Junio C Hamano
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).