From: Sam Ravnborg <sam@ravnborg.org>
To: Jeff Garzik <jeff@garzik.org>,
Nico Schottelius <nico-linux-20090330@schottelius.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: setlocalversion bug [Was: Linux 2.6.30-rc6]
Date: Sat, 16 May 2009 10:48:01 +0200 [thread overview]
Message-ID: <20090516084801.GA16044@uranus.ravnborg.org> (raw)
In-Reply-To: <4A0E62D4.5080004@garzik.org>
On Sat, May 16, 2009 at 02:53:08AM -0400, Jeff Garzik wrote:
>
> Strange version numbering.... x86-64/Fedora 10/2.6.30-rc6 with no
> local modifications or 'localversion' file, built straight from git:
>
> $ make -s oldconfig && make -sj17
> $ sudo make modules_install && sudo make install
> ...
> INSTALL /lib/firmware/edgeport/down2.fw
> INSTALL /lib/firmware/whiteheat_loader.fw
> INSTALL /lib/firmware/whiteheat.fw
> DEPMOD 2.6.30-rc6-00000-rc6
> sh /spare/repo/linux-2.6/arch/x86/boot/install.sh 2.6.30-rc6-00000-rc6
> arch/x86/boot/bzImage \
> System.map "/boot"
>
>
>
> "2.6.30-rc6-00000-rc6" seems like something is broken, as building a
> released version from git always gave me a proper "2.6.30-rc5"-style
> version, as expected.
Hi Nico.
This looks like something introduced by:
a182ad3d0f858f50bb719a48bb35a013e12366c5
("kbuild: fix scripts/setlocalversion with git")
Can you take a look at this.
Sam
next prev parent reply other threads:[~2009-05-16 8:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 4:36 Linux 2.6.30-rc6 Linus Torvalds
2009-05-16 6:53 ` Jeff Garzik
2009-05-16 8:48 ` Sam Ravnborg [this message]
2009-05-16 9:58 ` setlocalversion bug [Was: Linux 2.6.30-rc6] Nico Schottelius
2009-05-16 12:00 ` Nico Schottelius
2009-05-16 11:23 ` Linux 2.6.30-rc6 Alejandro Riveira Fernández
2009-05-16 20:35 ` Rafael J. Wysocki
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=20090516084801.GA16044@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nico-linux-20090330@schottelius.org \
--cc=torvalds@linux-foundation.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