All of lore.kernel.org
 help / color / mirror / Atom feed
From: Han Boetes <han@mijncomputer.nl>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] 2.6.9-ac1: invalid SUBLEVEL
Date: Thu, 21 Oct 2004 17:10:05 +0200	[thread overview]
Message-ID: <20041021151026.GP9258@boetes.org> (raw)
In-Reply-To: <1098365506.17096.23.camel@localhost.localdomain>

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

Here is some old shell-code I wrote for my kernel updating script: It
was especially written because you tend to forget this.

test_version () {
    # Sometimes Alan forgets to update the EXTRAVERSION in the Makefile;
    # then you destroy the previous version and the script fails :S
    cd $pwd/linux-$latest_stable
    # if EXTRAVERSION is for mm but not the current one.
    if [ -z "$(grep "EXTRAVERSION = -$mm_rest" Makefile)" \
        -a -z "$(grep "EXTRAVERSION = .*mm" Makefile)" ]; then
        warning 'Warning: I had to edit the versionnumber in the Makefile!'
        grep "EXTRAVERSION =" Makefile
        perl -pi -e "s#^EXTRAVERSION.*\n#EXTRAVERSION = -$mm_rest\n#" \
            Makefile || error
        grep "EXTRAVERSION =" Makefile
    fi
}

> I'll go and hide in a corner for a bit.

I think it is a better idea you add some checks to the script you use to
generate that patch.



# Han

  reply	other threads:[~2004-10-21 15:13 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 [this message]
2004-10-21 15:29     ` Dave Jones

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=20041021151026.GP9258@boetes.org \
    --to=han@mijncomputer.nl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.