From: David Sterba <dsterba@suse.cz>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs progs release 4.5.3
Date: Thu, 12 May 2016 11:23:34 +0200 [thread overview]
Message-ID: <20160512092334.GM29353@twin.jikos.cz> (raw)
In-Reply-To: <pan$d3395$7e2181c5$29bfc9d7$bdd12ab9@cox.net>
On Thu, May 12, 2016 at 09:14:44AM +0000, Duncan wrote:
> David Sterba posted on Wed, 11 May 2016 16:47:39 +0200 as excerpted:
>
> > btrfs-progs 4.5.2 have been released. A bugfix release.
>
> So 4.5.3 as stated in the subject line, or 4.5.2 as stated in the message
> body?
>
> Given that I'm on 4.5.2, it must be 4.5.3 that's just released. =:^)
The subject line is correct, I'm copying the previous release message
text and forgot to update the version everywhere.
prev parent reply other threads:[~2016-05-12 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 14:47 Btrfs progs release 4.5.3 David Sterba
[not found] ` <pan$d3395$7e2181c5$29bfc9d7$bdd12ab9@cox.net>
2016-05-12 9:23 ` David Sterba [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=20160512092334.GM29353@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=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).