public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	pjones@redhat.com, mchristie@redhat.com
Subject: Re: Linux 2.6.35-rc2
Date: Mon, 7 Jun 2010 14:14:55 -0400	[thread overview]
Message-ID: <20100607181455.GB16928@phenom.dumpdata.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1006070939210.3515@i5.linux-foundation.org>

On Mon, Jun 07, 2010 at 09:40:33AM -0700, Linus Torvalds wrote:
> 
> 
> On Mon, 7 Jun 2010, Konrad Rzeszutek Wilk wrote:
> > 
> > I am wondering what about git pull request that were sent before this
> > email but haven't been addressed yet? Specifically I am concerned
> > about: http://lkml.org/lkml/2010/6/2/301
> 
> It was sent to me after the merge window already closed, and seemed to 
> be about just new features. As a result, I entirely ignored it.

Ah, <sigh> I seem to have a knack for continously missing the merge
windows. Is it fair to state that:

 1). Once you send an email saying that Linux 2.6.35 is released, the
     merge window has opened.
 2). Then the the maintainers have two weeks to send you git pull
     request for new features.
 3). After the two weeks, it is rc1, and only bug-fixes are accepted?

  reply	other threads:[~2010-06-07 18:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-06  4:15 Linux 2.6.35-rc2 Linus Torvalds
2010-06-06 13:47 ` Torsten Kaiser
2010-06-06 13:52   ` Himanshu Chauhan
2010-06-06 14:19   ` Linus Torvalds
2010-06-06 15:04     ` Torsten Kaiser
2010-06-07  5:58       ` Alex Deucher
2010-06-07  6:09         ` Torsten Kaiser
2010-06-07  6:22           ` Dave Airlie
2010-06-07  6:32             ` Alex Deucher
2010-06-07  6:52               ` Dave Airlie
2010-06-07 17:28                 ` Torsten Kaiser
2010-06-07  6:23           ` Alex Deucher
2010-06-06 15:48     ` Tejun Heo
2010-06-06 15:52       ` Tejun Heo
2010-06-06 16:25         ` Torsten Kaiser
2010-06-07  1:03           ` Alessandro Suardi
2010-06-07  3:31             ` Linus Torvalds
2010-06-07  2:33           ` Dave Airlie
2010-06-07  3:01             ` Jeff Chua
     [not found]               ` <AANLkTinpJfxgCxiPFpzcxShitSSn9VwZ-rUz2wQz6FKS@mail.gmail.com>
     [not found]                 ` <AANLkTinLvHu98TuIbZkuRnfiwUNz2HXI2cS_3EtKFSGo@mail.gmail.com>
2010-06-07  3:17                   ` Jeff Chua
2010-06-07  5:58               ` Torsten Kaiser
2010-06-07  3:04             ` Alessandro Suardi
2010-06-06 15:58     ` Torsten Kaiser
2010-06-07 16:37 ` Konrad Rzeszutek Wilk
2010-06-07 16:40   ` Linus Torvalds
2010-06-07 18:14     ` Konrad Rzeszutek Wilk [this message]
2010-06-07 18:45       ` Linus Torvalds

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=20100607181455.GB16928@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchristie@redhat.com \
    --cc=pjones@redhat.com \
    --cc=torvalds@linux-foundation.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