From: Junio C Hamano <gitster@pobox.com>
To: Nikita Bobko <nikitabobko@gmail.com>
Cc: Jeff King <peff@peff.net>,
git@vger.kernel.org, Elijah Newren <newren@gmail.com>
Subject: Re: git read-tree doesn't accept tree-ish
Date: Mon, 23 Aug 2021 12:27:06 -0700 [thread overview]
Message-ID: <xmqq5yvwq7w5.fsf@gitster.g> (raw)
In-Reply-To: <CAMJzOtz_h0iEL1VQCFvvLzw3XnL+qM=f+BvkmsTU=ps+0VA7RA@mail.gmail.com> (Nikita Bobko's message of "Mon, 23 Aug 2021 21:10:33 +0200")
Nikita Bobko <nikitabobko@gmail.com> writes:
> `git checkout <hash> -- <path>` also doesn't work in my case because
> if any file is removed in `<hash>` but not in my HEAD then `git
> checkout` doesn't remove the file in my HEAD
Look for "--no-overlay" option in "git checkout", perhaps?
next prev parent reply other threads:[~2021-08-23 19:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 17:31 git read-tree doesn't accept tree-ish Nikita Bobko
2021-08-23 17:38 ` Elijah Newren
2021-08-23 18:53 ` Jeff King
2021-08-23 19:10 ` Nikita Bobko
2021-08-23 19:23 ` Elijah Newren
2021-08-23 19:27 ` Junio C Hamano [this message]
2021-08-23 19:38 ` Nikita Bobko
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=xmqq5yvwq7w5.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--cc=nikitabobko@gmail.com \
--cc=peff@peff.net \
/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).