From: "Merlin Büge" <toni@bluenox07.de>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Question about behaviour of git-checkout --patch option
Date: Wed, 27 May 2020 12:32:34 +0200 [thread overview]
Message-ID: <20200527123234.737efc3f.toni@bluenox07.de> (raw)
In-Reply-To: <20200527080009.GB4006373@coredump.intra.peff.net>
On Wed, 27 May 2020 04:00:09 -0400
Jeff King <peff@peff.net> wrote:
> Trying your case with:
>
> git -c add.interactive.usebuiltin=true checkout -p master .
>
> shows that it does not list the added file at all. I suspect the form of
> the fix will be similar, but it may have to plumb through the file
> addition from the diff layer, as well.
Thanks a lot for your explanation! Good to know what's going on there.
Out of curiosity: How does the git community keep track of open bugs?
On https://git-scm.com/ I read that bug reports should be just send to
the mailing list. But if they are not fixed within a few days, wouldn't
they just get lost...?
Thanks.
--
Merlin Büge
next prev parent reply other threads:[~2020-05-27 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 20:11 Question about behaviour of git-checkout --patch option Merlin Büge
2020-05-27 7:56 ` Jeff King
2020-05-27 1:49 ` Johannes Schindelin
2020-05-27 8:00 ` Jeff King
2020-05-27 10:32 ` Merlin Büge [this message]
2020-05-27 4:48 ` Johannes Schindelin
2020-05-27 21:27 ` Merlin Büge
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=20200527123234.737efc3f.toni@bluenox07.de \
--to=toni@bluenox07.de \
--cc=git@vger.kernel.org \
--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).