From: Sam Ravnborg <sam@ravnborg.org>
To: Matt Mackall <mpm@selenic.com>
Cc: Christoph Hellwig <hch@waste.org>,
sam@ravnborg.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] read EXTRAVERSION from file
Date: Sat, 11 Sep 2004 00:11:29 +0200 [thread overview]
Message-ID: <20040910221129.GC11338@mars.ravnborg.org> (raw)
In-Reply-To: <20040910215353.GO5414@waste.org>
On Fri, Sep 10, 2004 at 04:53:53PM -0500, Matt Mackall wrote:
> On Mon, Aug 30, 2004 at 05:14:05PM +0200, Christoph Hellwig wrote:
> > The're an very interesting patch in the Debian tree still from the time
> > where Herbert Xu mentioned it, it allows creating a file .extraversion
> > in the toplevel kernel directory and the Makefile will set EXTRAVERSION
> > to it's contents. This has the nice advantage of keeping an
> > extraversion pre-tree instead of having to patch the Makefile and
> > getting rejects everytime you pull a new tree (or BK refuses to touch
> > the Makefile).
> >
> > The only thing I'm not fully comfortable is the .extraversion name, I
> > think I'd prefer a user-visible name.
> >
> > Any other comments on this one?
>
> (catching up)
>
> Consider this approach as a more flexible alternative:
>
> http://groups.google.com/groups?q=oxymoron+patch+names&hl=en&lr=&ie=UTF-8&selm=fa.jif8l5v.1b049jd%40ifi.uio.no&rnum=1
Did something remotely similar.
Name the file localversion* and it will be in KERNELRELEASE.
Sam
prev parent reply other threads:[~2004-09-10 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 15:14 [PATCH] read EXTRAVERSION from file Christoph Hellwig
2004-08-30 15:35 ` Muli Ben-Yehuda
2004-08-30 16:18 ` Sam Ravnborg
2004-08-31 6:20 ` Frank Steiner
2004-09-10 21:53 ` Matt Mackall
2004-09-10 22:11 ` Sam Ravnborg [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=20040910221129.GC11338@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=hch@waste.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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 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.