From: Piotr Krukowiecki <email@example.com>
Subject: Checkout file without changing index?
Date: Wed, 24 Apr 2019 15:37:05 +0200 [thread overview]
Message-ID: <CAA01CsoJZMJ86mpybukqT0hVnvXi0FuRjZ23akM5kNPBdT754Q@mail.gmail.com> (raw)
what is the standard/recommended way for updating a file to given version?
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.
After searching a bit I found "git show revision:file > file". But
1. works only for 1 file. "git show revision -- file" does something else
2. requires full path, so you need to specify "git show
If there's no other easy way, maybe we could add "--no-index" to
checkout: "git checkout --no-index revision -- file" (or similar -
maybe use options from git-reset).
My use case: I had some changes prepared in index and wanted to
compare the prepared version with some older version. The file was a
zip file plus we use LFS so there was no other way than to "checkout"
the file, unpack it and diff it.
next reply other threads:[~2019-04-24 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 13:37 Piotr Krukowiecki [this message]
2019-04-24 13:46 ` Checkout file without changing index? Junio C Hamano
2019-04-24 18:15 ` Piotr Krukowiecki
2019-04-24 20:16 ` Philip Oakley
2019-04-25 3:40 ` Sitaram Chamarty
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).