From: Stefan Smietanowski <stesmi@stesmi.com>
To: Zack Weinberg <zack@codesourcery.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-2.2.20a and gcc 3.0 ?
Date: Mon, 05 Nov 2001 22:03:21 +0100 [thread overview]
Message-ID: <3BE6FE99.8020400@stesmi.com> (raw)
In-Reply-To: <20011104192024.H267@codesourcery.com> <3BE68F75.3010300@stesmi.com> <20011105120143.M267@codesourcery.com>
Hi!
>>I know how it's done, it's just that in my eyes a stable release is the
>>one where you know there's only 1 .... A 2.95.4 package built on
>>different days (from CVS) will differ. A 2.95.4 package built on
>>different ways from a .tar.gz marked as 'release' will not differ.
>>
>>For instance chasing a kernel bug is difficult when 1 person might use 1
>>version of a compiler and another uses a different version when both
>>says 2.95.4, no matter how miniscule the difference.
>>
>
> Since patches are being applied to the 2.95 branch at a rate of about
> one a month, I think the date stamp in the version number should be
> quite sufficient to avoid any problems along these lines.
If it's tested and rock stable, why isn't it released?
// Stefan
next prev parent reply other threads:[~2001-11-05 21:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-04 20:26 linux-2.2.20a and gcc 3.0 ? f5ibh
2001-11-04 20:38 ` Alan Cox
2001-11-04 22:11 ` Heinz Diehl
2001-11-04 23:13 ` Alex Buell
2001-11-05 1:25 ` Stefan Smietanowski
2001-11-05 3:20 ` Zack Weinberg
2001-11-05 13:09 ` Stefan Smietanowski
2001-11-05 20:01 ` Zack Weinberg
2001-11-05 21:03 ` Stefan Smietanowski [this message]
2001-11-05 21:45 ` Zack Weinberg
2001-11-05 9:58 ` Alex Buell
2001-11-05 11:47 ` ip autoconfig and e100 Ryan Sweet
2001-11-05 13:12 ` linux-2.2.20a and gcc 3.0 ? Stefan Smietanowski
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=3BE6FE99.8020400@stesmi.com \
--to=stesmi@stesmi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zack@codesourcery.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 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.