public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Hans Reiser <reiser@namesys.com>
Cc: 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: Fri, 19 Jul 2002 18:13:13 -0600	[thread overview]
Message-ID: <20020720001313.GJ10315@clusterfs.com> (raw)
In-Reply-To: <3D38A29C.9040901@namesys.com>

On Jul 20, 2002  03:37 +0400, Hans Reiser wrote:
> >my understanding is that core changes that aren't in by Halloween are
> >not going to be accepted until 2.7.  By pre-announcing the deadline,
> >it is hoped that people will have lots of time to submit things that are
> >ready for inclusion, as opposed to rushing to submit when the "freeze"
> >is announced all of a sudden.
>
> I, in my egocentrism, think it would make more sense to have a deadline 
> for submission rather than a deadline for acceptance, as that would make 
> things predictable for patch submitters, and avoid unintentional 
> overlooking of good patches from obscure persons due to the crush of 
> patches in October.
> 
> Pre-announcing the deadline is good, but having it be a deadline on 
> something the patch submitters control (submission time not acceptance 
> time) would be even better.

I would agree, except that this doesn't put any onus on the submitters
to get their patches in early, and causes the thundering heard of
patches problem the same way that not announcing the patch deadline does.

Note that "accepted" may be a bad term on my part - I can't say if this
means that the patch has been recieved by Linus, or whether it actually
has to be in the kernel tree at that date.

Note that I wasn't at the kernel summit myself, hence this is all just
what I have heard from others.

Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/


      parent reply	other threads:[~2002-07-20  0:12 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
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 [this message]

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=20020720001313.GJ10315@clusterfs.com \
    --to=adilger@clusterfs.com \
    --cc=Martin.Bligh@us.ibm.com \
    --cc=boissiere@adiglobal.com \
    --cc=hohnbaum@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    /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