From: Zack Weinberg <zack@codesourcery.com>
To: Stefan Smietanowski <stesmi@stesmi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-2.2.20a and gcc 3.0 ?
Date: Mon, 5 Nov 2001 12:01:43 -0800 [thread overview]
Message-ID: <20011105120143.M267@codesourcery.com> (raw)
In-Reply-To: <20011104192024.H267@codesourcery.com> <3BE68F75.3010300@stesmi.com>
In-Reply-To: <3BE68F75.3010300@stesmi.com>
On Mon, Nov 05, 2001 at 02:09:09PM +0100, Stefan Smietanowski wrote:
>
> 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.
zw
next prev parent reply other threads:[~2001-11-05 20:02 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 [this message]
2001-11-05 21:03 ` Stefan Smietanowski
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=20011105120143.M267@codesourcery.com \
--to=zack@codesourcery.com \
--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;
as well as URLs for NNTP newsgroup(s).