From: Dave Jones <davej@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Adrian Bunk <bunk@stusta.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] 2.6.9-ac1: invalid SUBLEVEL
Date: Thu, 21 Oct 2004 11:29:30 -0400 [thread overview]
Message-ID: <20041021152930.GH26170@redhat.com> (raw)
In-Reply-To: <1098365506.17096.23.camel@localhost.localdomain>
On Thu, Oct 21, 2004 at 02:31:47PM +0100, Alan Cox wrote:
> On Iau, 2004-10-21 at 13:49, Adrian Bunk wrote:
> > VERSION = 2
> > PATCHLEVEL = 6
> > -SUBLEVEL = 9-ac1
> > -EXTRAVERSION =
> > +SUBLEVEL = 9
> > +EXTRAVERSION = -ac1
> > NAME=AC 1
>
> Doh I'm -amazed- that worked for me. Fixed in my tree, I'll go and hide
> in a corner for a bit.
I think we can forgive you Alan, clearly you're out of practise 8-)
Dave
prev parent reply other threads:[~2004-10-21 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 11:08 Linux 2.6.9-ac1 Alan Cox
2004-10-21 12:49 ` [patch] 2.6.9-ac1: invalid SUBLEVEL Adrian Bunk
2004-10-21 13:31 ` Alan Cox
2004-10-21 15:10 ` Han Boetes
2004-10-21 15:29 ` Dave Jones [this message]
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=20041021152930.GH26170@redhat.com \
--to=davej@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.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