All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hugo Mills <hugo-lkml@carfax.org.uk>
To: helmut@hullen.de
Cc: linux-btrfs@vger.kernel.org
Subject: Re: version (was: btrfs, broken design?)
Date: Fri, 21 Jan 2011 12:21:19 +0000	[thread overview]
Message-ID: <20110121122119.GA811@carfax.org.uk> (raw)
In-Reply-To: <BeHcMN1T1uB@helmut.hullen.de>

[-- Attachment #1: Type: text/plain, Size: 1485 bytes --]

On Fri, Jan 21, 2011 at 10:54:00AM +0100, Helmut Hullen wrote:
> Hallo, Chris,
> 
> Du meintest am 20.01.11:
> 
> >> Is there a planned date for the final release of btrfs?
> 
> > A final release?  We'll keep improving things for a long time.  The
> > biggest missing feature today is btrfsck, which I'm working on full
> > time right now.
> 
> Could it be possible to tell somewhere the actual version?
> 
> Sometimes I download via git,
> 
>  <git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs-unstable.git>

> and I never have found which version that is; "version.sh" tells  
> something wrong.

$ git log

   then look at the revision ID of the top commit -- that's the
closest thing to a version number we've got. When you build from the
git repository, the version number that the tools report will be
something like 0.19-36-g70c6c10. This means that it's 36 commits on
from the version tagged as 0.19, and the last commit was g70c6c10.

   (This is for the userspace tools, of course -- the kernel has a
similar numbering scheme, if you're not building from Linus's tagged
versions).

> And I never have seen somethin like "Changelog" - that would be fine  
> too.

$ git log

   :)

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
       --- He's playing Schubert.  I think Schubert is losing. ---       

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2011-01-21 12:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 21:06 btrfs, broken design? Benoît Thiébault
2011-01-20 21:20 ` Chris Mason
2011-01-21  5:25   ` Benoît Thiébault
2011-01-21  6:46     ` Chester
2011-01-21  8:11       ` Benoît Thiébault
2011-01-21  8:21         ` Hubert Kario
2011-01-21  9:54   ` version (was: btrfs, broken design?) Helmut Hullen
2011-01-21 12:21     ` Hugo Mills [this message]
2011-01-21 14:10       ` version Helmut Hullen
2011-01-21 14:32     ` version (was: btrfs, broken design?) Diego Calleja
2011-01-21 14:55       ` version Helmut Hullen
2011-01-21 15:12         ` version Hugo Mills
2011-01-21 15:19           ` version Helmut Hullen
2011-01-24  3:20         ` version Chris Samuel
2011-01-24  8:33           ` version Helmut Hullen
2011-01-24 21:14             ` version Johannes Hirte
2011-01-24 21:39               ` version Helmut Hullen
2011-01-24 22:46                 ` version Chris Samuel
2011-01-25  1:03                   ` version Chris Mason
2011-01-25  6:43                   ` version Helmut Hullen
2011-01-25 14:37                   ` version Helmut Hullen
2011-01-27  5:02                     ` 2.6.38-rc2 oops's when rebalancing on different size drives (was Re: version) Chris Samuel
2011-01-27  7:45                     ` version Chris Mason
2011-01-27  8:16                       ` version Helmut Hullen
2011-01-27 13:28                       ` version Helmut Hullen
2011-01-27 13:49                       ` no space left (was: version) Helmut Hullen
2011-01-26 10:13       ` version (was: btrfs, broken design?) Erik Logtenberg
2011-01-26 14:13         ` Diego Calleja

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=20110121122119.GA811@carfax.org.uk \
    --to=hugo-lkml@carfax.org.uk \
    --cc=helmut@hullen.de \
    --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 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.