From: "Björn Gustavsson" <bgustavsson@gmail.com>
To: Raman Gupta <rocketraman@fastmail.fm>
Cc: Nanako Shiraishi <nanako3@lavabit.com>,
git@vger.kernel.org, trast@student.ethz.ch, gitster@pobox.com
Subject: Re: [PATCHv3] Add branch management for releases to gitworkflows
Date: Sat, 14 Nov 2009 09:59:44 +0100 [thread overview]
Message-ID: <6672d0160911140059r78dda7bbvbd3cc67828dc4322@mail.gmail.com> (raw)
In-Reply-To: <4AFE41AF.8050802@fastmail.fm>
On Sat, Nov 14, 2009 at 6:35 AM, Raman Gupta <rocketraman@fastmail.fm> wrote:
>
> Ok, another dumb question: since you have now submitted a patch on top
> of my patch, what is the proper etiquette for proceeding? Who
> maintains this patch series until it is committed? Since your patch
> applies on top of mine I can't really make any more changes without
> affecting your patch right? I can't find any guidance in the
> SubmittingPatches document.
I can't answer the questions about proper etiquette, but you *can* do
more changes
if you first apply Nanako's patch on top of your previous changes.
/Björn
--
Björn Gustavsson, Erlang/OTP, Ericsson AB
next prev parent reply other threads:[~2009-11-14 9:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 19:46 Add branch management for releases to gitworkflows rocketraman
2009-11-12 19:46 ` [PATCHv3] " rocketraman
2009-11-12 20:08 ` skillzero
2009-11-12 20:30 ` Raman Gupta
2009-11-13 22:19 ` Nanako Shiraishi
2009-11-13 22:56 ` Raman Gupta
2009-11-13 23:10 ` Nanako Shiraishi
2009-11-14 5:35 ` Raman Gupta
2009-11-14 8:59 ` Björn Gustavsson [this message]
2009-11-14 9:01 ` Nanako Shiraishi
2009-11-14 17:27 ` Raman Gupta
2009-11-15 9:14 ` Junio C Hamano
2009-11-15 17:07 ` Thomas Rast
2009-11-18 0:19 ` Raman Gupta
2009-11-18 14:59 ` Thomas Rast
2009-11-19 4:11 ` Nanako Shiraishi
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=6672d0160911140059r78dda7bbvbd3cc67828dc4322@mail.gmail.com \
--to=bgustavsson@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nanako3@lavabit.com \
--cc=rocketraman@fastmail.fm \
--cc=trast@student.ethz.ch \
/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).