From: Adrian Bunk <bunk@stusta.de>
To: Matt LaPlante <kernel1@cyberdogtech.com>
Cc: "'Randy Dunlap'" <rdunlap@xenotime.net>,
"'David Lang'" <dlang@digitalinsight.com>,
linux-kernel@vger.kernel.org
Subject: Re: How long to wait on patches?
Date: Sat, 22 Jul 2006 18:09:24 +0200 [thread overview]
Message-ID: <20060722160924.GQ25367@stusta.de> (raw)
In-Reply-To: <000401c6ad2e$a6ba0eb0$fe01a8c0@cyberdogt42>
On Fri, Jul 21, 2006 at 09:32:09PM -0400, Matt LaPlante wrote:
>
> Adrian has a trivial git tree which has been silent for a couple weeks too.
> This is part of the reason I was curious if the patches were still sitting
> in his inbox or if they'd been passed over. Of course, that's a question
> only he could answer.
I'm only forwarding trivial patches to Linus during the two weeks
merging phase before -rc1.
Until then, they are sitting in my "trivial" mail folder.
> Matt
cu
Adrian
BTW: If you are expecting an answer from me, putting me in the Cc would
make me faster aware of your email.
--
"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-07-22 16:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-22 1:26 How long to wait on patches? Randy Dunlap
2006-07-22 1:32 ` Matt LaPlante
2006-07-22 16:09 ` Adrian Bunk [this message]
2006-09-25 14:52 ` Matt LaPlante
2006-09-26 23:45 ` Adrian Bunk
2006-09-28 0:54 ` Matt LaPlante
2006-09-28 1:01 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2006-07-22 2:07 Randy Dunlap
2006-07-22 1:07 Randy Dunlap
2006-07-22 1:18 ` Matt LaPlante
2006-07-22 0:50 Matt LaPlante
2006-07-21 22:45 ` David Lang
2006-07-22 1:45 ` 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=20060722160924.GQ25367@stusta.de \
--to=bunk@stusta.de \
--cc=dlang@digitalinsight.com \
--cc=kernel1@cyberdogtech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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