From: Jeff King <peff@peff.net>
To: Michele Locati <michele@locati.it>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] filter-branch: return 2 when nothing to rewrite
Date: Thu, 15 Mar 2018 12:24:58 -0400 [thread overview]
Message-ID: <20180315162457.GA31351@sigill.intra.peff.net> (raw)
In-Reply-To: <CAGen01hodC=z_74z+7fSSrx2kvPnSbOQaML9kBb9iO6xCvWHQA@mail.gmail.com>
On Thu, Mar 15, 2018 at 05:18:59PM +0100, Michele Locati wrote:
> Great! So, I'm ready to update the patch, including the doc changes,
> which will be
> the one suggested by Jeff:
> [...]
Sounds good.
> And yes, I'm a brand new contributor, so here's my question: how should I
> send an updated patch? I can't find anything related to this in
> https://github.com/git/git/blob/master/Documentation/SubmittingPatches
Usually you'd just send it in reply to the original thread with "[PATCH
v2]" instead of just "[PATCH]" in the subject line. If you're using
format-patch or send-email, you should be able to just add "-v2" (and
--in-reply-to if you want to join the existing thread).
I thought SubmittingPatches discussed patch "re-rolls" like this, but I
don't see any mention of it from a quick grep.
-Peff
next prev parent reply other threads:[~2018-03-15 16:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 13:03 [PATCH] filter-branch: return 2 when nothing to rewrite Michele Locati
2018-03-15 14:12 ` Jeff King
2018-03-15 14:57 ` Michele Locati
2018-03-15 15:35 ` Jeff King
2018-03-15 15:42 ` Junio C Hamano
2018-03-15 15:48 ` Jeff King
2018-03-15 15:55 ` Junio C Hamano
2018-03-15 16:18 ` Michele Locati
2018-03-15 16:24 ` Jeff King [this message]
2018-03-15 17:09 ` [PATCH v2] " Michele Locati
2018-03-15 17:58 ` Junio C Hamano
2018-03-15 17:59 ` 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=20180315162457.GA31351@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=michele@locati.it \
/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).