All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Justin Lebar <jlebar@google.com>
Cc: "Jason St. John" <jstjohn@purdue.edu>, git <git@vger.kernel.org>,
	Richard Hansen <rhansen@bbn.com>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	Jeff King <peff@peff.net>, Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCH 3/4] Fix misuses of "nor" in comments. (v3)
Date: Mon, 31 Mar 2014 15:00:54 -0700	[thread overview]
Message-ID: <xmqqtxae2fl5.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAMuNMfpnojdQi4x_M_k29GBsq_i282Zph3AgLgsZv4arxB3CfA@mail.gmail.com> (Justin Lebar's message of "Mon, 31 Mar 2014 14:04:43 -0700")

Justin Lebar <jlebar@google.com> writes:

> Thanks; fixed in v4 (just sent out).

I only saw [3/4] that was marked with (v3) at the end, without
[{1,2,4}/4].  As you seem to be renumbering from the very original
(which had "l10n" at number 3), only sending out what you changed,
expecting that everybody else knows what you are doing, is not very
friendly to anybody who is trying not to lose patches in all the
other activities on the list.  Also people who haven't seen the
older iterations do not have to fish them from the archive if you
repost the whole thing.

Please use "format-patch -v5" (or whatever numbering) so that the
series iteration number is inside, e.g. [PATCH v5 1/6].

Thanks.

      reply	other threads:[~2014-03-31 22:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-29 22:59 [PATCH 3/4] Fix misuses of "nor" in comments. (v3) Justin Lebar
2014-03-31 19:54 ` Jason St. John
2014-03-31 21:04   ` Justin Lebar
2014-03-31 22:00     ` Junio C Hamano [this message]

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=xmqqtxae2fl5.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jlebar@google.com \
    --cc=jrnieder@gmail.com \
    --cc=jstjohn@purdue.edu \
    --cc=peff@peff.net \
    --cc=rhansen@bbn.com \
    --cc=spearce@spearce.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.