From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Tim Schmielau <tim@physik3.uni-rostock.de>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: why are some of my patches being credited to other "authors"?
Date: Sat, 9 Dec 2006 08:16:37 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0612090813080.13873@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.63.0612091327540.24913@gockel.physik3.uni-rostock.de>
On Sat, 9 Dec 2006, Tim Schmielau wrote:
> i wrote:
> > but given that i'm trying to follow the kernel guidelines and keep
> > each submission as a logically-related chunk, in many cases, i
> > have to wait for one patch to be applied before i can submit the
> > next one. and, at the moment, there's no way of knowing what's
> > going on.
>
> Well, you can send out a patch series:
> [patch 01/02] Prepare foo for blah
> [patch 02/02] Apply blah to foo
> Ideally you would finish the patch description for patch 02 with something
> like
>
> ---
> This patch depends on [patch 01/02] Prepare foo for blah
... snip ...
wait a minute. that's not what i've understood all this time as the
rationale for a multi-part patch -- to show dependency. certainly,
that's not what you read in "SubmittingPatches":
"If one patch depends on another patch in order for a change to be
complete, that is OK. Simply note "this patch depends on patch X" in
your patch description."
that doesn't say anything about using the multi-part notation. are
you sure about this?
rday
next prev parent reply other threads:[~2006-12-09 13:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 10:22 Robert P. J. Day
2006-12-09 11:29 ` Benjamin Herrenschmidt
2006-12-09 12:05 ` Robert P. J. Day
2006-12-09 12:39 ` Tim Schmielau
2006-12-09 13:16 ` Robert P. J. Day [this message]
2006-12-09 13:55 ` Jesper Juhl
2006-12-09 11:34 ` Jeff Garzik
2006-12-09 12:11 ` Robert P. J. Day
2006-12-09 21:40 ` Stefan Richter
2006-12-10 5:09 ` Paul Mundt
2006-12-10 19:19 ` Adrian Bunk
2006-12-09 13:48 ` Pekka Enberg
2006-12-10 7:24 ` Andrew Morton
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=Pine.LNX.4.64.0612090813080.13873@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@physik3.uni-rostock.de \
/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
all inboxes | Powered by JetHome®