mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Bryan Wu <cooloney.lkml@gmail.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
	Michal Simek <simekm2@fel.cvut.cz>,
	linux-kernel@vger.kernel.org, monstr@monstr.eu
Subject: Re: New linux arch
Date: Tue, 08 Jan 2008 18:05:41 +0100	[thread overview]
Message-ID: <4783AD65.5040005@s5r6.in-berlin.de> (raw)
In-Reply-To: <386072610801080100w30b7c6dar773e47de1472a030@mail.gmail.com>

Bryan Wu wrote:
> On Jan 8, 2008 4:49 PM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
>> On Jan 8, 2008 10:28 AM, Bryan Wu <cooloney.lkml@gmail.com> wrote:
>> > 1. Push patches to LKML when merge window open (2 weeks after a stable
>> > kernel version release, for example 2 weeks after 2.6.24 released)
>>
>> You shouldn't wait for the merge window to open to send patches for
>> review for the first time; otherwise you'll just miss the opportunity
>> to merge ;-).
>>
> 
> Really? I was told before to send out big patch to LKML for the merge window.
> If not, it's good news for Michal and MicroBlaze guys.

There aren't any fixed windows for development, review, testing, and so
on.  There is only Linus' merge window for the merge process of the
patches that have been reviewed, tested, and pre-integrated.

Of course people like akpm and the maintainers of the larger subsystems
necessarily align their own work with Linus', therefore there may be
periods around merge windows during which relevant people won't
integrate larger submissions.  But that does not mean you could not post
them.
-- 
Stefan Richter
-=====-==--- ---= -=---
http://arcgraph.de/sr/

  reply	other threads:[~2008-01-08 17:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 11:29 Michal Simek
2008-01-07 12:34 ` Sam Ravnborg
2008-01-07 12:51   ` Michal Simek
2008-01-07 19:16     ` Sam Ravnborg
2008-01-07 12:47 ` Pekka Enberg
2008-01-07 13:00   ` Michal Simek
2008-01-07 13:12     ` Pekka Enberg
2008-01-07 13:34   ` Jan Engelhardt
2008-01-07 17:26     ` Stefan Richter
2008-01-07 17:39       ` Jan Engelhardt
2008-01-07 17:54         ` H. Peter Anvin
2008-01-07 18:20   ` Stefan Richter
2008-01-07 22:00 ` Benjamin Herrenschmidt
2008-01-07 22:39   ` Michal Simek
2008-01-08  8:28 ` Bryan Wu
2008-01-08  8:49   ` Pekka Enberg
2008-01-08  9:00     ` Bryan Wu
2008-01-08 17:05       ` Stefan Richter [this message]
2008-01-08 17:12   ` Stefan Richter
2008-01-09  1:16 ` Arnd Bergmann

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=4783AD65.5040005@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=cooloney.lkml@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=monstr@monstr.eu \
    --cc=penberg@cs.helsinki.fi \
    --cc=simekm2@fel.cvut.cz \
    /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®