From: Ben Greear <greearb@candelatech.com>
To: unlisted-recipients:; (no To-header on input)@pop.zip.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux-2.4.x patch submission policy (what about the -AC series?)
Date: Sat, 06 Jan 2001 13:12:13 -0700 [thread overview]
Message-ID: <3A577C1D.F57B2DD0@candelatech.com> (raw)
In-Reply-To: <937neu$p95$1@penguin.transmeta.com>
Linus Torvalds wrote:
>
> I thought I'd mention the policy for 2.4.x patches so that nobody gets
> confused about these things. In some cases people seem to think that
> "since 2.4.x is out now, we can relax, go party, and generally goof
> off".
>
> Not so.
Sounds like a perfectly valid argument to me. Since Alan Cox's branch
seems to take on some of the more experimental stuff, perhaps it could
be used as an outlet for the pent-up patches untill 2.5 comes out?
Alan, could you elucidate your policy for accepting patches into the -ac
series?
Thanks,
Ben
--
Ben Greear (greearb@candelatech.com) http://www.candelatech.com
Author of ScryMUD: scry.wanfear.com 4444 (Released under GPL)
http://scry.wanfear.com http://scry.wanfear.com/~greear
-
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/
next prev parent reply other threads:[~2001-01-06 19:09 UTC|newest]
Thread overview: 15+ 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 ` Ben Greear [this message]
2001-01-07 16:37 ` Rik van Riel
2001-01-08 21:33 ` Ingo Oeser
2001-01-08 21:33 ` Ingo Oeser
2001-01-08 20:40 ` Rik van Riel
2001-01-08 20:40 ` Rik van Riel
2001-01-09 4:00 ` Eric W. Biederman
2001-01-10 11:12 ` Roeland Th. Jansen
2001-01-10 11:12 ` Roeland Th. Jansen
2001-01-16 19:55 ` Does reiserfs really meet the "Linux-2.4.x patch submission policy"? André Dahlqvist
2001-01-16 20:25 ` 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=3A577C1D.F57B2DD0@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.