From: "Roeland Th. Jansen" <roel@grobbebol.xs4all.nl>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Linux-2.4.x patch submission policy
Date: Wed, 10 Jan 2001 11:12:07 +0000 [thread overview]
Message-ID: <20010110111207.A4231@grobbebol.xs4all.nl> (raw)
In-Reply-To: <20010108223343.O10035@nightmaster.csn.tu-chemnitz.de> <Pine.LNX.4.21.0101081837520.21675-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0101081837520.21675-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Mon, Jan 08, 2001 at 06:40:21PM -0200
On Mon, Jan 08, 2001 at 06:40:21PM -0200, Rik van Riel wrote:
> I wasn't aware Andrea switched the way he stored his patches
> lately ;)
he's doing that for quite some time now (for suse's kernels too) and
that works pretty well :-)
> OTOH, the advantage of having a big patch means that it's
> easier for me to get people to test all of the things I
> have. Guess I'll need to find a way to easily get both the
> small and the big patches ;)
the trouble with that is also that the whole patch must be checked again
and again if a new version is being sent out. Andrea's patches have th
epossibility to be applied for several versions and indeed are easy to
use -- apply what you want.
it made SMP testing more fun compared to the big patches where nobody
exactly knows what patch may have caused [in]stability.
I for instance have the daunting task to check why 2.4.0 here crashes so
easily without messages, except some occasional APIC error. yuck.
--
Grobbebol's Home | Don't give in to spammers. -o)
http://www.xs4all.nl/~bengel | Use your real e-mail address /\
Linux 2.2.16 SMP 2x466MHz / 256 MB | on Usenet. _\_v
-
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-10 14:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-06 18:17 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 [this message]
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=20010110111207.A4231@grobbebol.xs4all.nl \
--to=roel@grobbebol.xs4all.nl \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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
all inboxes | Powered by JetHome®