mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Matt LaPlante" <kernel1@cyberdogtech.com>
To: "'Randy Dunlap'" <rdunlap@xenotime.net>,
	"'David Lang'" <dlang@digitalinsight.com>,
	<linux-kernel@vger.kernel.org>
Subject: RE: How long to wait on patches?
Date: Fri, 21 Jul 2006 21:32:09 -0400	[thread overview]
Message-ID: <000401c6ad2e$a6ba0eb0$fe01a8c0@cyberdogt42> (raw)
In-Reply-To: <1153531563.25640@shark.he.net>



> -----Original Message-----
> From: Randy Dunlap [mailto:rdunlap@xenotime.net]
> Sent: Friday, July 21, 2006 9:26 PM
> To: Matt LaPlante; 'Randy Dunlap'; 'David Lang'; linux-
> kernel@vger.kernel.org
> Subject: RE: How long to wait on patches?
> 
> 
> 
> > > -----Original Message-----
> > > From: Randy Dunlap [mailto:rdunlap@xenotime.net]
> > > Sent: Friday, July 21, 2006 9:07 PM
> > > To: David Lang; Matt LaPlante; linux-kernel@vger.kernel.org
> > > Subject: Re: How long to wait on patches?
> > >
> > >
> > >
> > > > On Fri, 21 Jul 2006, Matt LaPlante wrote:
> > > >
> > > >[me]
> > > >
> > > > 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
> >
> > Yes, my patches were CC'd to the trivial alias.  I guess from what
> I've read
> > on that page that I should wait until after .18 to look for them in
> the git?
> 
> You mean in Linus's git tree?  Adrian will have to answer that
> question, although the answer is likely to be Yes.  Linus recently
> said that he accepts patches until -rc2 and after that he is
> looking for stability and bug fixes for a final release, so
> it could well be after 2.6.18 when they are merged.
> 
> ---
> ~Randy

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.

-
Matt



  reply	other threads:[~2006-07-22  1:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-22  1:26 Randy Dunlap
2006-07-22  1:32 ` Matt LaPlante [this message]
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
  -- 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='000401c6ad2e$a6ba0eb0$fe01a8c0@cyberdogt42' \
    --to=kernel1@cyberdogtech.com \
    --cc=dlang@digitalinsight.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

all inboxes | Powered by JetHome®