From: Adrian Bunk <bunk@stusta.de>
To: Paul Mundt <lethal@linux-sh.org>,
"Robert P. J. Day" <rpjday@mindspring.com>,
Jeff Garzik <jeff@garzik.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: why are some of my patches being credited to other "authors"?
Date: Sun, 10 Dec 2006 20:19:01 +0100 [thread overview]
Message-ID: <20061210191901.GF10351@stusta.de> (raw)
In-Reply-To: <20061210050920.GA19828@linux-sh.org>
On Sun, Dec 10, 2006 at 02:09:20PM +0900, Paul Mundt wrote:
>...
> trivial@kernel.org exists to handle the rest of the bits, where Adrian
> has a tendency to queue up many trivial and related patches at once, and
> sending out pull requests at a time where it will be less disruptive to
> the rest of development. You might be better off simply CC'ing trivial@
> on these patch submissions and routinely checking the trivial git tree to
> see whether they've been queued or not.
>...
Checking the tree won't help since it's only different from Linus' tree
in the few hours between me asking Linus to pull and Linus actually
pulling.
Patches to trivial@kernel.org simply go into a mail folder, and I'm
going through this during the two week merge window.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-12-10 19:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 10:22 why are some of my patches being credited to other "authors"? 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
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 [this message]
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=20061210191901.GF10351@stusta.de \
--to=bunk@stusta.de \
--cc=jeff@garzik.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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.