From: Junio C Hamano <gitster@pobox.com>
To: Jeremiah Mahler <jmmahler@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v8 0/2] format-patch --signature-file <file>
Date: Thu, 22 May 2014 12:00:39 -0700 [thread overview]
Message-ID: <xmqqy4xtmyeg.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140522142332.GA15095@hudson.localdomain> (Jeremiah Mahler's message of "Thu, 22 May 2014 07:23:32 -0700")
Jeremiah Mahler <jmmahler@gmail.com> writes:
> I just notice that my patch is in 'pu'.
> But it is version 7 instead of the improved version 8.
Yeah, I know. In a distributed environment, multiple people work
independently and a sequence of event can go like this:
- I read v7, comment, and queue it only so that I won't forget;
- I attend to other topics;
- I start the day's integration cycle, merging topics to the
integration branches, maint, master, next and pu;
- You reroll v8 and post it;
- I may not notice v8, or I may notice v8 but think it is not
worth to discard the integration work so far only to replace
v7 with v8.
- The integration result is pushed out.
A reminder is very much appreciated, but on the other hand it is not
something unusual. It happens all the time, and I usually am aware
of it ;-)
Thanks.
next prev parent reply other threads:[~2014-05-22 19:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 1:53 [PATCH v8 0/2] format-patch --signature-file <file> Jeremiah Mahler
2014-05-22 1:53 ` [PATCH v8 1/2] format-patch: make newline after signature conditional Jeremiah Mahler
2014-05-22 1:53 ` [PATCH v8 2/2] format-patch --signature-file <file> Jeremiah Mahler
2014-05-22 20:52 ` Junio C Hamano
2014-05-23 5:55 ` Jeremiah Mahler
2014-05-23 16:56 ` Junio C Hamano
2014-05-22 14:23 ` [PATCH v8 0/2] " Jeremiah Mahler
2014-05-22 19:00 ` Junio C Hamano [this message]
2014-05-22 19:41 ` Jeremiah Mahler
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=xmqqy4xtmyeg.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jmmahler@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 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.