linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gene Czarcinski <gene@czarc.net>
To: dsterba@suse.cz
Cc: chris.mason@fusionio.com, linux-btrfs@vger.kernel.org
Subject: Re: [GIT PULL] btrfs-progs: more bugfixes for 0.20-rc1
Date: Fri, 18 Jan 2013 10:49:20 -0500	[thread overview]
Message-ID: <50F96F00.3040008@czarc.net> (raw)
In-Reply-To: <20130118144439.GB19967@twin.jikos.cz>

On 01/18/2013 09:44 AM, David Sterba wrote:
> On Fri, Jan 18, 2013 at 09:16:00AM -0500, Gene Czarcinski wrote:
>>> Sergei Trofimovich (1):
>>>        version.sh: fix version when built from tarball
>> While you are about it, how about adding in this fix from Dieter Ries to fix
>> version a little more:
>> http://article.gmane.org/gmane.comp.file-systems.btrfs/20069
> I did not notice it before, but Dieter's patch does not work when progs
> are built from .git repository
>
> -echo "#define BTRFS_BUILD_VERSION \"Btrfs $v\"" >> .build-version.h
> +echo "#define BTRFS_BUILD_VERSION \"$v\"" >> .build-version.h
>
> $v is set with the git tag, so the "Btrfs" string does not appear in the
> output (eg. mkfs.btrfs).
>
> Technically, $v should always contain some sort of a tag, Sergei's patch
> hardcodes it to the latest one for the non-git case. This is IMHO the
> right approach.
>
OK, I see what you mean.  However, the current situation when btrfs is 
built from a tarball results in:

 >btrfs  --version
Btrfs Btrfs v0.19

and

 >mkfs.btrfs  -V
mkfs.btrfs, part of Btrfs Btrfs v0.19

There must be a way to reliably just have one "Btrfs" and I will look 
into it.

Gene

  reply	other threads:[~2013-01-18 15:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17 17:47 [GIT PULL] btrfs-progs: more bugfixes for 0.20-rc1 David Sterba
2013-01-17 17:51 ` Chris Mason
2013-01-18 17:32   ` Goffredo Baroncelli
2013-01-18 14:16 ` Gene Czarcinski
2013-01-18 14:44   ` David Sterba
2013-01-18 15:49     ` Gene Czarcinski [this message]
2013-01-18 15:55       ` Hugo Mills
2013-01-18 16:48         ` Gene Czarcinski
2013-01-18 15:33 ` Gene Czarcinski
2013-01-18 17:22   ` David Sterba
2013-01-18 21:02     ` Gene Czarcinski
2013-01-21 10:50       ` David Sterba

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=50F96F00.3040008@czarc.net \
    --to=gene@czarc.net \
    --cc=chris.mason@fusionio.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).