All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: LAST CALL FOR BTRFS-NEXT
Date: Wed, 20 Feb 2013 22:42:02 +0800	[thread overview]
Message-ID: <20130220144201.GD4941@liubo.jp.oracle.com> (raw)
In-Reply-To: <20130220142612.GA2062@localhost.localdomain>

On Wed, Feb 20, 2013 at 09:26:12AM -0500, Josef Bacik wrote:
> 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!

Hi Josef,

Thanks for your maintaining work.

Could you please pull this into btrfs-next?  I don't see new bug reports after
this version.

- Btrfs: snapshot-aware defrag
https://patchwork.kernel.org/patch/2058911/

thanks,
liubo

> 
> Josef
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-02-20 14:43 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 [this message]
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=20130220144201.GD4941@liubo.jp.oracle.com \
    --to=bo.li.liu@oracle.com \
    --cc=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 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.