From: Chris Mason <clm@fb.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.cz>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: cleanup the btrfs trees
Date: Mon, 21 Oct 2019 12:44:40 +0000 [thread overview]
Message-ID: <EF03F1BE-6060-48C3-B6AA-409F9355A52B@fb.com> (raw)
In-Reply-To: <20191020144731.20bc0633@canb.auug.org.au>
On 19 Oct 2019, at 23:47, Stephen Rothwell wrote:
> Hi all,
>
> The btrfs tree
> (git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git#next)
> has not bee updated in more than a year, so I have removed it and then
> renamed the btrfs-kdave tree to btrfs. I hope this is OK and if any
> other changes are needed, please let me know.
Thanks Stephen
-chris
prev parent reply other threads:[~2019-10-21 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 3:47 linux-next: cleanup the btrfs trees Stephen Rothwell
2019-10-21 12:44 ` Chris Mason [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=EF03F1BE-6060-48C3-B6AA-409F9355A52B@fb.com \
--to=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).