public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Matt LaPlante <kernel1@cyberdogtech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How long to wait on patches?
Date: Wed, 27 Sep 2006 01:45:05 +0200	[thread overview]
Message-ID: <20060926234505.GL4547@stusta.de> (raw)
In-Reply-To: <20060925105212.cf4985a7.kernel1@cyberdogtech.com>

On Mon, Sep 25, 2006 at 10:52:12AM -0400, Matt LaPlante wrote:

> 2.6.18 is out, so I feel the urge to revive a dead topic. :) Any idea when we might get my ancient trivials included in the new gits?  I'm still lurking around and ready to do more pointless doc-checking tasks, but I really want the old stuff merged so I can rebase around it.
>...

During the 2 weeks until 2.6.19-rc1.

It wouldn't be good if I'd forward all the trivial patches today 
probably breaking the context for pending merges.

> Matt

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


  reply	other threads:[~2006-09-26 23:45 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
2006-09-25 14:52     ` Matt LaPlante
2006-09-26 23:45       ` Adrian Bunk [this message]
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=20060926234505.GL4547@stusta.de \
    --to=bunk@stusta.de \
    --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