From: Junio C Hamano <gitster@pobox.com>
To: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, "Merlin Büge" <toni@bluenox07.de>,
"Jeff King" <peff@peff.net>,
"Johannes Schindelin" <johannes.schindelin@gmx.de>
Subject: Re: [PATCH] checkout -p: handle new files correctly
Date: Wed, 27 May 2020 14:51:01 -0700 [thread overview]
Message-ID: <xmqqwo4xjbcq.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <pull.646.git.1590613746507.gitgitgadget@gmail.com> (Johannes Schindelin via GitGitGadget's message of "Wed, 27 May 2020 21:09:06 +0000")
"Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
writes:
> This also fixes the problem where added _empty_ files could not be
> staged via `git checkout -p`.
Nice. Will queue.
> For ease of backporting, this patch is based on js/add-p-leftover-bits.
Yup, I agree that it would be a sensible fork point.
next prev parent reply other threads:[~2020-05-27 21:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 21:09 [PATCH] checkout -p: handle new files correctly Johannes Schindelin via GitGitGadget
2020-05-27 21:51 ` Junio C Hamano [this message]
2020-05-27 23:03 ` Jeff King
2020-05-27 19:51 ` Johannes Schindelin
2020-05-27 19:58 ` Johannes Schindelin
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=xmqqwo4xjbcq.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=johannes.schindelin@gmx.de \
--cc=peff@peff.net \
--cc=toni@bluenox07.de \
/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).