From: Josef Bacik <josef@redhat.com>
To: linux-btrfs@vger.kernel.org
Subject: Introducing btrfs-next
Date: Tue, 10 Apr 2012 13:15:13 -0400 [thread overview]
Message-ID: <20120410171512.GA1917@localhost.localdomain> (raw)
Hello,
In an effort to be a little bit better about reviewing patches sent to the
mailinglist I've created a btrfs-next git tree kernel.org. You can get it here
git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git
I'm going to be scraping the mailinglist every day for patches that are sent and
applying them to this tree in order to get some better testing throughout the
development cycle and possibly stop being such a lazy bum about reviewing. If
you are looking to get patches into the next merge window and you notice I
haven't included them in this tree please let me know so I can pull them in, I
did a very casual look through the list to find stuff so I probably missed
something. Thanks much,
Josef
reply other threads:[~2012-04-10 17:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120410171512.GA1917@localhost.localdomain \
--to=josef@redhat.com \
--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).