From: Chris Mason <chris.mason@fusionio.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Chris Mason <clmason@fusionio.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: [GIT PULL] Btrfs for linux-next
Date: Mon, 1 Oct 2012 21:36:18 -0400 [thread overview]
Message-ID: <20121002013618.GA1140@shiny> (raw)
In-Reply-To: <20121001181549.817cc2d7d0d660eb593922fd@canb.auug.org.au>
On Mon, Oct 01, 2012 at 02:15:49AM -0600, Stephen Rothwell wrote:
> Hi Chris,
>
> On Sun, 30 Sep 2012 07:52:58 -0400 Chris Mason <chris.mason@fusionio.com> wrote:
> >
> > This is our large queue of changes for linux-next. They vary from bug
> > fixes to huge optimizations. It also includes a new disk format feature
> > from suse to remove a restriction on the number of hardlinks to a single
> > file in a single dir.
> >
> > I tested against linux-next on Friday, it was a clean merge and passes
> > xfstests.
> >
> > Just let me know if there are any problems, thanks! The changes are in
> > my next branch
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git next
>
> I added your tree today, but as you have seen it broke :-(
Hi Steve,
Sorry for the hassle, we've updated that patch and rebased the tree:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git next
-chris
next prev parent reply other threads:[~2012-10-02 1:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120930115258.GA13506@shiny>
2012-10-01 8:15 ` [GIT PULL] Btrfs for linux-next Stephen Rothwell
2012-10-02 1:36 ` Chris Mason [this message]
2012-10-02 2:54 ` Stephen Rothwell
2012-10-02 12:26 ` 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=20121002013618.GA1140@shiny \
--to=chris.mason@fusionio.com \
--cc=clmason@fusionio.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.