From: Sam Ravnborg <sam@ravnborg.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] kill two dead headers
Date: Tue, 07 Oct 2003 20:46:32 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106555967513001@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106451477025244@msgid-missing>
On Tue, Oct 07, 2003 at 11:44:49AM -0500, Alan Mayer wrote:
>
> It would simplify our lives enormously if none of these patches were applied, with the possible
> exception of the last two. They're pretty much stomping all over work already in progress or
> introducing bugs that we don't really have the time or resources to track down and fix.
Reading the above it occurs to me you are aiming for "flag-day patches".
Try to keep in sync with main-line instead is a *much* better approach.
If you are having troubles getting your patches applied, maybe it's
due to the size anyway.
See how Martin does it for S390 for example. 5-20 paches each 3 weeks in
average. And he gets good feedback - also from others than hch.
Developing everything in vacuum is the wrong approach, and does not
give you any feedback from the community - or at least you get it
only indirect with patches that hch creates.
Sam
next prev parent reply other threads:[~2003-10-07 20:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 18:08 [PATCH] kill two dead headers Christoph Hellwig
2003-10-07 16:44 ` Alan Mayer
2003-10-07 20:46 ` Sam Ravnborg [this message]
2003-10-07 21:20 ` Alan Mayer
2003-10-08 13:15 ` Christoph Hellwig
2003-10-08 16:40 ` Alan Mayer
2003-10-08 16:46 ` Christoph Hellwig
2003-10-08 17:30 ` Jesse Barnes
2003-10-09 20:36 ` David Mosberger
2003-10-10 9:28 ` Christoph Hellwig
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=marc-linux-ia64-106555967513001@msgid-missing \
--to=sam@ravnborg.org \
--cc=linux-ia64@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.