public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: André Dahlqvist <anedah-9@sm.luth.se>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Does reiserfs really meet the "Linux-2.4.x patch submission policy"?
Date: Tue, 16 Jan 2001 20:55:58 +0100	[thread overview]
Message-ID: <20010116205558.A1171@sm.luth.se> (raw)
In-Reply-To: <937neu$p95$1@penguin.transmeta.com>
In-Reply-To: <937neu$p95$1@penguin.transmeta.com>; from torvalds@transmeta.com on Sat, Jan 06, 2001 at 10:17:02AM -0800

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1468 bytes --]

Hi Linus

I was very surprised when I checked my local kernel.org mirror this
morning, and noticed that the latest 2.4.1 pre-patch had grown to
~180 kb in size. I was even more surprised when I realized that the
inclusion of reiserfs was the reason for this. While I am certainly
happy for the reiserfs guys, I can't help but wondering if this really
had to happen for 2.4.1.

In my understanding of your "2.4.x patch sumission guidelines" these
large patches was exactly what you wanted to avoid at this point in
time. For example, isn't reiserfs to be considered a "more involved
patch" the way you described it in this e-mail:

On Sat, Jan 06, 2001 at 10:17:02AM -0800, Linus Torvalds wrote:

> In short, releasing 2.4.0 does not open up the floor to just about
> anything.  In fact, to some degree it will probably make patches _less_
> likely to be accepted than before, at least for a while.  I want to be
> absolutely convicned that the basic 2.4.x infrastructure is solid as a
> rock before starting to accept more involved patches. 

Don't get me wrong, I am personally really excited that reiserfs was
included. I just thought that you basically wanted 2.4.1 to be "boring".

I guess it's the "pushover and wimp" showing his face again:-)
-- 

André Dahlqvist <anedah-9@sm.luth.se>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-01-16 19:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-06 18:17 Linux-2.4.x patch submission policy Linus Torvalds
2001-01-06 19:33 ` Alan Cox
2001-01-06 20:12 ` Linux-2.4.x patch submission policy (what about the -AC series?) Ben Greear
2001-01-07 16:37 ` Linux-2.4.x patch submission policy Rik van Riel
2001-01-08 21:33   ` Ingo Oeser
2001-01-08 20:40     ` Rik van Riel
2001-01-10 11:12       ` Roeland Th. Jansen
2001-01-16 19:55 ` André Dahlqvist [this message]
2001-01-16 20:25   ` Does reiserfs really meet the "Linux-2.4.x patch submission policy"? Linus Torvalds
2001-01-17  1:05   ` Aaron Lehmann
2001-01-17  1:14     ` 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=20010116205558.A1171@sm.luth.se \
    --to=anedah-9@sm.luth.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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