From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: kusmabite@gmail.com, git@vger.kernel.org,
matthieu.moy@grenoble-inp.fr, hellmuth@ira.uka.de
Subject: Re: [PATCH] add -p: skip conflicted paths
Date: Wed, 4 Apr 2012 16:25:27 -0400 [thread overview]
Message-ID: <20120404202527.GA1363@sigill.intra.peff.net> (raw)
In-Reply-To: <7vty0z8i66.fsf@alter.siamese.dyndns.org>
On Wed, Apr 04, 2012 at 11:29:21AM -0700, Junio C Hamano wrote:
> >> So combining the two patches, we have
> >> something like:
> >
> > Hrm. I kind of liked the idea of doing this with a single plumbing call
> > to diff-files (the entries that come from --raw will be mostly discarded
> > except for the ones that are marked with "U"), though.
>
> That is, something like this on top of your patch.
Ugh, I totally misread your original message and missed the fact that we
_could_ see what we wanted by adding "--raw". Sorry to be dense.
Yes, this is way better. I don't mind discarding the --raw entries that
are not used; they cost nothing to generate on top of what we are
already doing, so it is really just the cost of shuttling a few bytes
across the pipe.
> - for (run_cmd_pipe(qw(git diff-files --numstat --summary --), @tracked)) {
> + for (run_cmd_pipe(qw(git diff-files --numstat --summary),
> + ($note_unmerged ? ("--raw") : ()),
> + "--", @tracked)) {
Maybe it is not worth even having $note_unmerged, and just filling in
the UNMERGED field unconditionally? I know other callers don't care
about the information, but it's so cheap, and it just makes the function
interface that much simpler.
-Peff
next prev parent reply other threads:[~2012-04-04 20:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 19:18 [PATCH] add -p: skip conflicted paths Erik Faye-Lund
2012-03-28 19:28 ` Junio C Hamano
2012-03-28 20:20 ` Erik Faye-Lund
2012-03-28 21:39 ` Junio C Hamano
2012-03-28 21:58 ` Junio C Hamano
2012-03-28 22:14 ` Junio C Hamano
2012-03-29 5:45 ` Jeff King
2012-04-02 17:20 ` Erik Faye-Lund
2012-04-02 18:25 ` Junio C Hamano
2012-04-04 9:46 ` Jeff King
2012-04-04 12:50 ` Tay Ray Chuan
2012-04-04 15:36 ` Junio C Hamano
2012-04-04 18:29 ` Junio C Hamano
2012-04-04 20:25 ` Jeff King [this message]
2012-04-04 21:31 ` Junio C Hamano
2012-04-05 12:30 ` Jeff King
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=20120404202527.GA1363@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hellmuth@ira.uka.de \
--cc=kusmabite@gmail.com \
--cc=matthieu.moy@grenoble-inp.fr \
/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).