mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Stefan Smietanowski <stesmi@stesmi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Some thoughts about stable kernel development
Date: 13 Nov 2003 20:55:37 +0100	[thread overview]
Message-ID: <m3wua411s6.fsf@defiant.pm.waw.pl> (raw)
In-Reply-To: <3FB333B2.2090006@stesmi.com>

Stefan Smietanowski <stesmi@stesmi.com> writes:

> x.y.z+1 pre/rc q does not contain
> something that x.y.z pre/rc r has is NOT easy. We both know that
> me and you will have no problem whatsoever with this scheme. So it's
> not about me and you. I just think it will confuse some people that's
> all.

That's correct. It seems I have misunderstood your previous email.

This scheme aims for less workload on the maintainers (compared to
different test + stable trees, as with many popular projects) -
the added bit of complexity at least seems to scale well.

Users already have to live with 2.5.1 being a little older than 2.4.22.

testing/* patches are IMHO not for people who may have problems (bigger
than just a moment of confusion) with such things - they will have much
more problems reporting a bug should they found one.

I know this isn't an ideal solution, that's the best I'm currently aware
of: we'd gain much shorter devel cycle at a really small cost.
I agree entirely with Alan and his opinion expressed in this thread.
-- 
Krzysztof Halasa, B*FH

  reply	other threads:[~2003-11-14 20:56 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-09 18:41 Krzysztof Halasa
2003-11-09 19:05 ` Valdis.Kletnieks
2003-11-12 15:05   ` Krzysztof Halasa
2003-11-09 19:06 ` Stefan Smietanowski
2003-11-12 15:07   ` Krzysztof Halasa
2003-11-12 16:04     ` Stefan Smietanowski
2003-11-12 16:51       ` Krzysztof Halasa
2003-11-13  7:33         ` Stefan Smietanowski
2003-11-13 19:55           ` Krzysztof Halasa [this message]
2003-11-09 19:26 ` Andrew Morton
2003-11-09 20:34   ` Alan Cox
2003-11-09 20:41   ` Maciej Zenczykowski
2003-11-09 19:29 ` Willy Tarreau
2003-11-12 15:01   ` Krzysztof Halasa
2003-11-09 19:50 ` John Bradford
2003-11-09 23:49   ` Valdis.Kletnieks
2003-11-10  8:53     ` John Bradford
2003-11-09 23:54   ` Rob Landley
2003-11-10  8:50     ` John Bradford
2003-11-11  7:47       ` Ryan Anderson
2003-11-11  8:19       ` Valdis.Kletnieks
2003-11-11  8:53         ` John Bradford
2003-11-10 10:58 ` Marcelo Tosatti
2003-11-12 14:48   ` Krzysztof Halasa
2003-11-10 13:35 ` jlnance
2003-11-12 14:43   ` Krzysztof Halasa
2003-11-10 16:54 ` Adrian Bunk
2003-11-12 14:40   ` Krzysztof Halasa
2003-11-09 21:53 Matt

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=m3wua411s6.fsf@defiant.pm.waw.pl \
    --to=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stesmi@stesmi.com \
    /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®