From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs send in 3.12 : can't find snapshot?
Date: Mon, 16 Dec 2013 10:34:25 +0000 (UTC) [thread overview]
Message-ID: <pan$85bb8$3e67585f$45c93b97$25e14599@cox.net> (raw)
In-Reply-To: 87y53lqx88.fsf@maru2.md5i.com
Michael Welsh Duggan posted on Sun, 15 Dec 2013 22:40:55 -0500 as
excerpted:
> I built the new btrfs-progs 3.12 recently. I note that the version
> information doesn't seem to match this:
>
> # ./btrfs --version Btrfs v0.20-rc1-358-g194aa4a
I see Wang Shilong dealt with the snapshot issue; I'll tackle the version
thing.
There was a bit of a hiccup in the versioning with the 3.12 tarball,
since the version policy had just changed with it, and (I gather) the
tarball prep script hadn't been updated appropriately. I believe a patch
has already been applied to fix the problem (the patch was certainly
posted on this list, but I haven't tracked whether it was actually
applied yet) so the same problem won't happen the next time.
Meanwhile, btrfs properly reports v3.12 here, but I pull and build from
live-git, and the v3.12 tagged commit simply happened to still be current
HEAD last I updated. That does explain why the problem with the tarball
version wasn't discovered earlier, however, since people (including the
devs) building from live-git saw the expected v3.12; it was apparently
only the process of preparing and releasing the tarball that was affected
by the version bug.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2013-12-16 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 3:40 btrfs send in 3.12 : can't find snapshot? Michael Welsh Duggan
2013-12-16 6:18 ` Wang Shilong
2013-12-17 1:28 ` Michael Welsh Duggan
2013-12-17 2:16 ` Wang Shilong
2013-12-17 11:51 ` Wang Shilong
2013-12-16 10:34 ` Duncan [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='pan$85bb8$3e67585f$45c93b97$25e14599@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).