From: Josef Bacik <jbacik@fusionio.com>
To: <linux-btrfs@vger.kernel.org>
Subject: LAST CALL FOR BTRFS-NEXT
Date: Wed, 20 Feb 2013 09:26:12 -0500 [thread overview]
Message-ID: <20130220142612.GA2062@localhost.localdomain> (raw)
Hello,
If you have patches in btrfs-next, make sure they are the right ones so we don't
have to rebase and repull and merge and all that crap for this merge window. If
I'm missing stuff that's fine, I can throw that on top, but you need to make
sure I have the right versions of stuff already in the tree so I can rebase it
_now_ rather than trying to figure out how to fix it later. Thanks!
Josef
next reply other threads:[~2013-02-20 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 14:26 Josef Bacik [this message]
2013-02-20 14:42 ` LAST CALL FOR BTRFS-NEXT Liu Bo
2013-02-20 15:12 ` David Sterba
2013-02-20 15:35 ` Alex Lyakas
2013-02-20 15:39 ` Chris Mason
2013-02-21 15:20 ` Filipe Brandenburger
2013-02-21 15:46 ` Chris Mason
2013-02-21 17:55 ` Filipe Brandenburger
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=20130220142612.GA2062@localhost.localdomain \
--to=jbacik@fusionio.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