From: Chris Mason <chris.mason@fusionio.com>
To: Alex Lyakas <alex.btrfs@zadarastorage.com>
Cc: Josef Bacik <JBacik@fusionio.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: LAST CALL FOR BTRFS-NEXT
Date: Wed, 20 Feb 2013 10:39:01 -0500 [thread overview]
Message-ID: <20130220153901.GB21291@shiny.masoncoding.com> (raw)
In-Reply-To: <CAOcd+r3Qk+bAAS3ZVzF826MPpSEFHe5Z1U8vMFKwPJyVUw-qTA@mail.gmail.com>
On Wed, Feb 20, 2013 at 08:35:30AM -0700, Alex Lyakas wrote:
> Hi Josef,
> can you please consider including these two patches from Jan 28:
> https://patchwork.kernel.org/patch/2057051/
> https://patchwork.kernel.org/patch/2057071/
>
> I realize they have "V2" label, although the cover letter had "V3",
> this was my bad. However, they both apply to what you have now in
> btrfs-next.
It's really ok if we add more after I pull in the current next, but I
don't want to have to rebase the current next again. So, I'd rather
that we focus on patches currently in -next and make sure they are the
correct versions etc.
-chris
next prev parent reply other threads:[~2013-02-20 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 14:26 LAST CALL FOR BTRFS-NEXT Josef Bacik
2013-02-20 14:42 ` Liu Bo
2013-02-20 15:12 ` David Sterba
2013-02-20 15:35 ` Alex Lyakas
2013-02-20 15:39 ` Chris Mason [this message]
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=20130220153901.GB21291@shiny.masoncoding.com \
--to=chris.mason@fusionio.com \
--cc=JBacik@fusionio.com \
--cc=alex.btrfs@zadarastorage.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.