All of lore.kernel.org
 help / color / mirror / Atom feed
From: BandiPat <magicpage91@earthlink.net>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] add a snapshot version string to GRUB title
Date: Thu, 02 Jul 2009 21:51:05 -0400	[thread overview]
Message-ID: <4A4D6409.3000905@earthlink.net> (raw)
In-Reply-To: <1246567148.20370.5.camel@mj>

Pavel Roskin wrote:
> On Thu, 2009-07-02 at 22:20 +0200, Christian Franke wrote:
>> Many "GNU GRUB  version 1.96" used in production are likely builds from 
>> more recent SVN snapshots. It would (IMO) be useful to have some info 
>> about the actual installed version.
> 
> I can tell from my experience with other projects that such suggestions
> appear when there is not enough leadership in the project, and nobody
> cares about producing stable releases.
> 
> It would be better to produce named prereleases or release candidates if
> we are not comfortable about releasing 1.97 right now.
> 
===========
I do think the world is ready for another stable release number, like 
1.97 or 2.0, but in the mean time, I've been doing this in my build script.

echo "-- Starting Autogen.sh... --"
sed -e "s/,\[1\.96\],/,[$softversion],/" -i configure.ac
./autogen.sh

Where basically the $softversion is your svn number I label the build 
as.  The above replaces the 1.96 found in the title bar with "svn2383" 
or whatever the svn number is at the time, so users will know what they 
are using.

But again, why not put a freeze on adding things, just fix the bugs so 
you can release a stable version number for those squeamish about using svn?

Regards,
Pat



  parent reply	other threads:[~2009-07-03  1:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02 20:20 [PATCH] add a snapshot version string to GRUB title Christian Franke
2009-07-02 20:39 ` Pavel Roskin
2009-07-02 21:51   ` Vladimir 'phcoder' Serbinenko
2009-07-03  1:51   ` BandiPat [this message]
2009-07-03 17:31     ` Pavel Roskin

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=4A4D6409.3000905@earthlink.net \
    --to=magicpage91@earthlink.net \
    --cc=grub-devel@gnu.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.