From: Jean Delvare <khali@linux-fr.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Andrey Borzenkov <arvidjaar@mail.ru>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Andy Whitcroft <apw@shadowen.org>,
Herbert Poetzl <herbert@13thfloor.at>,
Olaf Hering <olaf@aepfle.de>
Subject: Re: .version keeps being updated
Date: Wed, 10 Jan 2007 18:10:53 +0100 [thread overview]
Message-ID: <20070110181053.3b3632a8.khali@linux-fr.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0701101426400.14458@scrub.home>
Hi Roman,
On Wed, 10 Jan 2007 14:45:28 +0100 (CET), Roman Zippel wrote:
> On Tue, 9 Jan 2007, Jean Delvare wrote:
>
> > I tried a git bisect to find out what commit was reponsible for it, and
> > the winner is...
> >
> > 8993780a6e44fb4e7ed34e33458506a775356c6e is first bad commit
> > commit 8993780a6e44fb4e7ed34e33458506a775356c6e
> > Author: Linus Torvalds <torvalds@woody.osdl.org>
> > Date: Mon Dec 11 09:28:46 2006 -0800
> >
> > [..]
> > Reverting this from 2.6.20-rc1 made the build behave again, however I
> > found that reverting it from 2.6.20-rc2 did _not_ fix the problem. I
> > also had to revert the following patch to make things work as before
> > again:
> >
> > commit ef129412b4cbd6686d0749612cb9b76e207271f4
> > Author: Andrew Morton <akpm@osdl.org>
> > Date: Fri Dec 22 01:12:01 2006 -0800
>
> To make the list complete, this patch started all the mess:
>
> commit a2ee8649ba6d71416712e798276bf7c40b64e6e5
> Author: Herbert Poetzl <herbert@13thfloor.at>
> Date: Fri Dec 8 02:36:00 2006 -0800
>
> [PATCH] Fix linux banner utsname information
>
> and this tries to fix a problem in Andrew's patch:
>
> commit d449db98d5d7d90f29f9f6e091b0e1d996184df1
> Author: Mikael Pettersson <mikpe@it.uu.se>
> Date: Fri Dec 29 16:48:09 2006 -0800
>
> [PATCH] fix mrproper incompleteness
>
> The patch below reverts pretty much everything and instead introduces a
> seperate format string for proc.
> (...)
> [PATCH] fix linux banner format string
>
> Revert previous attempts at messing with the linux banner string and
> simply use a separate format string for proc.
This fixes the problem I reported. Thanks Roman!
Linus, Andrew, if Roman's patch looks OK to you, can it please be
applied before 2.6.20 is released?
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2007-01-10 17:10 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 9:20 .version keeps being updated Jean Delvare
2007-01-09 9:32 ` Gene Heskett
2007-01-09 17:05 ` Andrey Borzenkov
2007-01-09 20:44 ` Jean Delvare
2007-01-09 21:31 ` Andrew Morton
2007-01-09 23:21 ` Linus Torvalds
2007-01-09 23:25 ` Andrew Morton
2007-01-09 23:33 ` David Miller
2007-01-09 23:39 ` Andi Kleen
2007-01-10 1:43 ` Herbert Poetzl
2007-01-10 8:53 ` Jean Delvare
2007-01-10 16:52 ` Martin J. Bligh
2007-01-10 17:05 ` Jean Delvare
2007-01-10 11:31 ` Jan Engelhardt
2007-01-10 13:45 ` Roman Zippel
2007-01-10 16:01 ` Olaf Hering
2007-01-10 17:10 ` Jean Delvare [this message]
2007-01-10 19:02 ` Linus Torvalds
2007-01-10 19:31 ` Olaf Hering
2007-01-10 20:02 ` Olaf Hering
2007-01-10 22:56 ` Jan Engelhardt
2007-01-10 23:35 ` Segher Boessenkool
2007-01-11 13:27 ` Jan Engelhardt
2007-01-11 13:55 ` Andreas Schwab
2007-01-11 17:39 ` Segher Boessenkool
2007-01-11 18:01 ` Jan Engelhardt
2007-01-10 21:33 ` Linus Torvalds
2007-01-10 19:32 ` Linus Torvalds
2007-01-10 21:20 ` Andy Whitcroft
2007-01-11 10:56 ` Andy Whitcroft
2007-01-11 12:38 ` Roman Zippel
2007-01-11 13:05 ` Andy Whitcroft
2007-01-11 16:47 ` Linus Torvalds
2007-01-09 21:55 ` Luca Tettamanti
2007-01-10 7:34 ` Jean Delvare
2007-01-09 23:25 ` Willy Tarreau
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=20070110181053.3b3632a8.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=arvidjaar@mail.ru \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=torvalds@osdl.org \
--cc=zippel@linux-m68k.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