linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Linux-2.4.x patch submission policy
Date: Mon, 8 Jan 2001 22:33:44 +0100	[thread overview]
Message-ID: <20010108223343.O10035@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0101071434370.21675-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Sun, Jan 07, 2001 at 02:37:47PM -0200

On Sun, Jan 07, 2001 at 02:37:47PM -0200, Rik van Riel wrote:
> Once we are sure 2.4 is stable for just about anybody I
> will submit some of the really trivial enhancements for
> inclusion; all non-trivial patches I will maintain in a
> VM bigpatch, which will be submitted for inclusion around
> 2.5.0 and should provide one easy patch for those distribution
> vendors who think 2.4 VM performance isn't good enough for
> them ;)

Hmm, could you instead follow Andreas approach and have a
directory with little patches, that do _exactly_ one thing and a
file along to describe what is related, dependend and what each
patch does?

So people could try to suit them to their needs.

And they can tell you exactly _what_ change breaks instead of "It
doesn't work".

Thanks & Regards

Ingo Oeser
-- 
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
         <<<<<<<<<<<<       come and join the fun       >>>>>>>>>>>>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

       reply	other threads:[~2001-01-08 21:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <937neu$p95$1@penguin.transmeta.com>
     [not found] ` <Pine.LNX.4.21.0101071434370.21675-100000@duckman.distro.conectiva>
2001-01-08 21:33   ` Ingo Oeser [this message]
2001-01-08 20:40     ` Rik van Riel
2001-01-09  4:00       ` Eric W. Biederman
2001-01-10 11:12       ` Roeland Th. Jansen

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=20010108223343.O10035@nightmaster.csn.tu-chemnitz.de \
    --to=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