All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Nigel Cunningham <ncunningham@cyclades.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
	linux-kernel@vger.kernel.org, stable@kernel.org,
	torvalds@osdl.org
Subject: Re: Linux 2.6.16.14
Date: Fri, 5 May 2006 07:20:42 +0200	[thread overview]
Message-ID: <20060505052042.GA28568@w.ods.org> (raw)
In-Reply-To: <200605051502.53481.ncunningham@cyclades.com>

On Fri, May 05, 2006 at 03:02:47PM +1000, Nigel Cunningham wrote:
> Hi Willy.
(snip)
> 
> I didn't mention it previously - I guess because it was subconscious - but I'm 
> looking at things from the point of view of someone maintaining an 
> out-of-tree patch. With almost all of these revisions, my patch continues to 
> apply cleanly, but I still get people asking "Is the patch for 2.6.16.9" safe 
> to apply against "2.6.16.9+x"? I simply don't have the time to continually 
> test and check, but I end up feeling like there's a new 2.6.x release 
> everyday that I just have to keep up with, because that's what the stable 
> users want. Maybe it just proves that I should hurry up and get the git tree 
> finished so I get try to get Suspend2 merged :)

Oh yes, I understand your problem, I went through that for several years with
2.4. Another advantage of many small updates is that the risk of conflict is
minor, and your users might often be able to apply the official patch *after*
your patch, which is very convenient.

Maybe you should just run a cron script to patch your kernels everytime a
new fix goes out, so that you'll at least be able to reply to your users
whether it's supposed to work or not.

> Regards,
> 
> Nigel

Regards,
Willy


  reply	other threads:[~2006-05-05  5:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-05  0:35 Linux 2.6.16.14 Chris Wright
2006-05-05  0:42 ` Chris Wright
2006-05-05  1:52 ` Nigel Cunningham
2006-05-05  2:20   ` Ioan Ionita
2006-05-05  2:33   ` Chris Wright
2006-05-05  2:47     ` Alistair John Strachan
2006-05-08 19:02       ` Bill Davidsen
2006-05-09 19:18         ` [stable] " Chris Wright
2006-05-05  3:03     ` Nigel Cunningham
2006-05-05  3:18       ` Ioan Ionita
2006-05-05  3:42         ` Patrick McFarland
2006-05-05  3:25       ` Chris Wright
2006-05-05  3:33         ` CaT
2006-05-05  5:10           ` [stable] " Greg KH
2006-05-05  4:50       ` Willy Tarreau
2006-05-05  5:02         ` Nigel Cunningham
2006-05-05  5:20           ` Willy Tarreau [this message]
2006-05-05 13:29 ` Josh Boyer
2006-05-05 17:40   ` Chris Wright

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=20060505052042.GA28568@w.ods.org \
    --to=willy@w.ods.org \
    --cc=chrisw@sous-sol.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@cyclades.com \
    --cc=stable@kernel.org \
    --cc=torvalds@osdl.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.