mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Omkhar Arasaratnam <iamroot@ca.ibm.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	tgall@us.ibm.com, antonb@au1.ibm.com,
	Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [BUG] 2.6.11- sym53c8xx Broken on pp64
Date: Wed, 9 Mar 2005 18:25:56 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0503091821570.2530@ppc970.osdl.org> (raw)
In-Reply-To: <1110420620.32525.145.camel@gaston>



On Thu, 10 Mar 2005, Benjamin Herrenschmidt wrote:
> 
> BTW, Linus: Any chance you ever change something to version or
> extraversion in bk just after a release ? I know I already ask and it
> degenerated into a flamefest, and I don't know if that is specifically
> the case now, but I keep getting report of people saying "I have a bug
> in 2.6.xx" while in fact, they have some kind of bk clone of sometime
> after 2.6.xx...

The answer is the same: I'd still like to have somebody (preferably Sam)  
who is comfortable with all the build scripts get a revision-control-
specific version at build-time, so that BK users would get the top-of-tree 
key value, and other people could get some CVS revision or something.

I don't want to tag things just randomly, especially as it would be very
error-prone (read: I'd forget). A script that looks at the top revision,
and if it's not a tag, takes the key value and appends it to the build
version seems to be The Right Thing (tm). 

I have this dim memory that Sam might even have had some early trials, but 
maybe thats just wishful thinking.. Sam?

		Linus

  reply	other threads:[~2005-03-10  2:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-10  1:51 Omkhar Arasaratnam
2005-03-10  2:10 ` Benjamin Herrenschmidt
2005-03-10  2:25   ` Linus Torvalds [this message]
2005-03-10  5:06     ` Ryan Anderson
2005-03-10  5:40     ` Sam Ravnborg
2005-03-13  4:32       ` [PATCH] Auto-append localversion for BK users needs to use CONFIG_SHELL Ryan Anderson
2005-04-03 19:17         ` Sam Ravnborg
2005-03-10  3:11   ` [BUG] 2.6.11- sym53c8xx Broken on pp64 Omkhar Arasaratnam
2005-03-10  3:34     ` Omkhar Arasaratnam
2005-03-10  3:47       ` Linus Torvalds
2005-03-10  4:53         ` Omkhar Arasaratnam
2005-03-10  5:59         ` Benjamin Herrenschmidt
2005-03-10 12:17           ` Matthew Wilcox
2005-03-10 15:17             ` James Bottomley
2005-03-10 17:05               ` Omkhar Arasaratnam
2005-03-10 22:02                 ` Benjamin Herrenschmidt
2005-03-11 14:54                   ` Omkhar Arasaratnam
2005-03-13 20:32                   ` Omkhar Arasaratnam
2005-03-15 15:54                   ` Omkhar Arasaratnam
2005-03-15 23:38                     ` Benjamin Herrenschmidt

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=Pine.LNX.4.58.0503091821570.2530@ppc970.osdl.org \
    --to=torvalds@osdl.org \
    --cc=antonb@au1.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=iamroot@ca.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=tgall@us.ibm.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®