From: Eric Sunshine <sunshine@sunshineco.com>
To: Jeff King <peff@peff.net>
Cc: Victor Leschuk <vleschuk@accesssoftek.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
"gitster@pobox.com" <gitster@pobox.com>,
"john@keeping.me.uk" <john@keeping.me.uk>,
Victor Leschuk <vleschuk@gmail.com>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Subject: Re: [PATCH v6] Add git-grep threads param
Date: Mon, 16 Nov 2015 16:17:31 -0500 [thread overview]
Message-ID: <CAPig+cQMV-VJDff=VCeBqRLZC7Q42mu7T78_NK2TWLjEN-=cpw@mail.gmail.com> (raw)
In-Reply-To: <20151116135614.GA13471@sigill.intra.peff.net>
On Mon, Nov 16, 2015 at 8:56 AM, Jeff King <peff@peff.net> wrote:
> On Mon, Nov 16, 2015 at 05:11:16AM -0800, Victor Leschuk wrote:
>
>> The earlier version of this patch is already included in /pu branch,
>> however as we all agreed ($gmane/280299) we have changed the default
>> behavior and the meaning of "0". The question is: what is the right
>> way to include changes from patch v6 (this one) into already merged
>> patch to pu?
>
> Merging to "pu" does not really mean anything; it is simply that the
> maintainer has picked it up as a possible topic of interest. Patches can
> (and often are) still re-written in that state.
>
> Junio is on vacation for a few weeks, and I'm acting as maintainer in
> the interim. I've added your v6 to my pile of patches to look at, but I
> haven't gone over it carefully yet.
To be perfectly explicit: Patches in 'pu' get replaced wholesale by
newer versions, so you would simply send the new version of the patch
in its entirety (as you did with v6).
next prev parent reply other threads:[~2015-11-16 21:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 11:52 [PATCH v6] Add git-grep threads param Victor Leschuk
2015-11-16 13:11 ` Victor Leschuk
2015-11-16 13:56 ` Jeff King
2015-11-16 21:17 ` Eric Sunshine [this message]
2015-11-30 9:48 ` Victor Leschuk
2015-11-30 19:31 ` Duy Nguyen
2015-11-30 19:45 ` Duy Nguyen
2015-12-04 20:10 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2015-11-30 19:31 Eric Sunshine
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='CAPig+cQMV-VJDff=VCeBqRLZC7Q42mu7T78_NK2TWLjEN-=cpw@mail.gmail.com' \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=john@keeping.me.uk \
--cc=peff@peff.net \
--cc=torvalds@linux-foundation.org \
--cc=vleschuk@accesssoftek.com \
--cc=vleschuk@gmail.com \
/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).