public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Andreas Dilger <adilger@clusterfs.com>,
	Michael Hohnbaum <hohnbaum@us.ibm.com>,
	"Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
	Guillaume Boissiere <boissiere@adiglobal.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6] Most likely to be merged by Halloween... THE LIST]
Date: Sat, 20 Jul 2002 04:31:03 +0400	[thread overview]
Message-ID: <3D38AF47.2000106@namesys.com> (raw)
In-Reply-To: Pine.LNX.4.44L.0207192110161.12241-100000@imladris.surriel.com

Rik van Riel wrote:

>On Sat, 20 Jul 2002, Hans Reiser wrote:
>
>  
>
>>I, in my egocentrism, think it would make more sense to have a deadline
>>for submission rather than a deadline for acceptance,
>>    
>>
>
>It's both.  We all know Linus doesn't have the time to keep
>forward-porting our hundreds of patches so he can only include
>patches into his kernel that apply to the exact same tree he
>has at that day.
>
>This (and the fact that Linus gets far too much email and patches
>to look at old ones) is bound to make the Halloween deadline stick
>for both submission and acceptance.
>
>I hope.
>
>regards,
>
>Rik
>  
>
That could be dealt with by letting people resend feature containing 
patches that were first submitted by Halloween (forward porting them as 
things progress) until they get a rejection or Linus announces he has 
taken all that he wants from the queue.  

A thundering herd of patches is an opportunity, not a problem, unless 
they need to get applied by Halloween.;-)

-- 
Hans




  reply	other threads:[~2002-07-20  0:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3D3875D4.3090102@us.ibm.com>
2002-07-19 20:40 ` [2.6] Most likely to be merged by Halloween... THE LIST] Michael Hohnbaum
2002-07-19 21:28   ` Hans Reiser
2002-07-19 23:28     ` Andreas Dilger
2002-07-19 23:37       ` Hans Reiser
2002-07-20  0:11         ` Rik van Riel
2002-07-20  0:31           ` Hans Reiser [this message]
2002-07-20  0:46             ` Rik van Riel
2002-07-20  0:53               ` Hans Reiser
2002-07-20  1:08                 ` Rik van Riel
2002-07-20  1:55                   ` Hans Reiser
2002-07-20  3:10                     ` Oliver Xymoron
2002-07-20  5:03                       ` Hans Reiser
2002-07-21 18:01                     ` Marcin Dalecki
2002-07-30 14:43                       ` Bill Davidsen
2002-07-30 14:46                         ` Marcin Dalecki
2002-07-30 15:52                           ` Hans Reiser
2002-07-20  0:13         ` Andreas Dilger

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=3D38AF47.2000106@namesys.com \
    --to=reiser@namesys.com \
    --cc=Martin.Bligh@us.ibm.com \
    --cc=adilger@clusterfs.com \
    --cc=boissiere@adiglobal.com \
    --cc=hohnbaum@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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