From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Chris Mason <clm@fb•com>, Josef Bacik <josef@toxicpanda•com>,
David Sterba <dsterba@suse•cz>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: linux-next: cleanup the btrfs trees
Date: Sun, 20 Oct 2019 14:47:31 +1100 [thread overview]
Message-ID: <20191020144731.20bc0633@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 326 bytes --]
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.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-10-20 3:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 3:47 Stephen Rothwell [this message]
2019-10-21 12:44 ` linux-next: cleanup the btrfs trees Chris Mason
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=20191020144731.20bc0633@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=clm@fb$(echo .)com \
--cc=dsterba@suse$(echo .)cz \
--cc=josef@toxicpanda$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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