From: "Randy Dunlap" <rdunlap@xenotime.net>
To: David Lang <dlang@digitalinsight.com>,
Matt LaPlante <kernel1@cyberdogtech.com>,
linux-kernel@vger.kernel.org
Subject: Re: How long to wait on patches?
Date: Fri, 21 Jul 2006 18:07:27 -0700 [thread overview]
Message-ID: <1153530447.22255@shark.he.net> (raw)
> On Fri, 21 Jul 2006, Matt LaPlante wrote:
>
> > I checked the FAQ but didn't see an answer to this. Over the past
few weeks
> > I've submitted probably around 8 simple typo-fix patches all of
which seemed
> > to be approved by others on the list. I've been following the GIT,
but these
> > patches haven't been merged yet. I know people are busy with other
things,
> > probably more important, but I would like to know how long is
"acceptable" to
> > wait before I should re-submit a patch. Obviously if enough time
passes,
> > patches start to break as source files change. I don't mean to be a
nuisance;
> > I'm just trying to determine proper protocol. That and the fact I
can submit
> > several more patches once I get some of these old ones out of my
queue. :)
>
> be sure to watch the -mm tree as well, a lot of patches are picked up
by Andrew
> to be fed to Linus that way
>
> this is a particularly bad week since almost all the core developers
were up at
> OLS.
>
> one thing you may want to look at doing (hosting permitting) is to
setup a git
> tree to just hold your trivial patches so that they can be pulled easily.
>
> I thought there was a person who was maintaining a -trivial tree for this
> purpose, I don't remember who it was though.
Yes, Adrian Bunk accepts and forwards trivial patches. See
http://www.kernel.org/pub/linux/kernel/people/bunk/trivial/
---
~Randy
next reply other threads:[~2006-07-22 1:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-22 1:07 Randy Dunlap [this message]
2006-07-22 1:18 ` How long to wait on patches? Matt LaPlante
-- strict thread matches above, loose matches on Subject: below --
2006-07-22 2:07 Randy Dunlap
2006-07-22 1:26 Randy Dunlap
2006-07-22 1:32 ` Matt LaPlante
2006-07-22 16:09 ` Adrian Bunk
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
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=1153530447.22255@shark.he.net \
--to=rdunlap@xenotime.net \
--cc=dlang@digitalinsight.com \
--cc=kernel1@cyberdogtech.com \
--cc=linux-kernel@vger.kernel.org \
/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