From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Len Brown <len.brown@intel.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Versioning of tree
Date: Thu, 21 Oct 2004 11:38:06 +1000 [thread overview]
Message-ID: <1098322686.21028.22.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.58.0410200728040.2317@ppc970.osdl.org>
On Thu, 2004-10-21 at 00:33, Linus Torvalds wrote:
> Personally, I much rather go the way we have gone, because I don't care
> about module versioning nearly as much as I care about bug-report
> versioning. And if I hear about a bug with 2.6.10-rc1, I want to know that
> it really is at _least_ 2.6.10-rc1, if you see what I mean..
I have the same problem with reports. I'm not talking about -rc*, that
is fine, I know that a report against rc-* means and most user will usually
tell me rc*-bk* so that's ok.
The problem is just with this intermediate state between 2.6.N "final" and
whatever gets next until we go to -rc. The fact that it has the exact same
version as 2.6.N final means that I get confusing reports (and, but I know
you don't care about modules, but it's simply impossible to have both
the "final" modules and the "current top of tree" modules installed at the
same time, which _is_ painful).
When I was still doing my "pmac" tree, what I would do was to put -pre0
in the EXTRAVERSION after a release until I got to -preX or -rcX...
Anyway, it's your call.
Ben.
next prev parent reply other threads:[~2004-10-21 1:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 6:49 Versioning of tree Benjamin Herrenschmidt
2004-10-20 7:22 ` Len Brown
2004-10-20 14:33 ` Linus Torvalds
2004-10-21 1:38 ` Benjamin Herrenschmidt [this message]
2004-10-21 15:33 ` Måns Rullgård
2004-10-21 15:48 ` Linus Torvalds
2004-10-21 16:49 ` Jeff Garzik
2004-10-21 17:10 ` Linus Torvalds
2004-10-21 23:03 ` kbuild (was Re: Versioning of tree) Jeff Garzik
2004-10-30 23:34 ` Sam Ravnborg
2004-10-25 23:47 ` Versioning of tree Ryan Anderson
2004-10-26 11:49 ` David Vrabel
2004-10-26 12:26 ` Ryan Anderson
2004-10-26 12:58 ` David Vrabel
2004-10-26 19:08 ` Sam Ravnborg
2004-10-26 18:04 ` Ryan Anderson
2004-10-26 19:11 ` Ian Campbell
2004-10-27 8:38 ` Ryan Anderson
2004-10-27 11:37 ` Sam Ravnborg
2004-10-20 8:22 ` Jeff Garzik
2004-10-20 8:39 ` Benjamin Herrenschmidt
2004-10-20 10:36 ` Måns Rullgård
-- strict thread matches above, loose matches on Subject: below --
2004-10-20 18:27 Chuck Ebbert
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=1098322686.21028.22.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox