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: Tue, 2 Oct 2012 08:26:53 -0400 [thread overview]
Message-ID: <20121002122653.GB1140@shiny> (raw)
In-Reply-To: <20121002125436.a39101ab6f87d4e8596c1031@canb.auug.org.au>
On Mon, Oct 01, 2012 at 08:54:36PM -0600, Stephen Rothwell wrote:
> Hi Chris,
>
> On Mon, 1 Oct 2012 21:36:18 -0400 Chris Mason <chris.mason@fusionio.com> wrote:
> >
> > 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
>
> Looks good today.
>
> I am not sure if you are aware of exactly how linux-next works: I will
> fetch that branch of your tree every morning, so any changes will be
> automatically incorporated into linux-next.
Thanks! I knew you'd pull again but wanted to send an explicit ack that
we had fixed up the first pull.
-chris
prev parent reply other threads:[~2012-10-02 12:26 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
2012-10-02 2:54 ` Stephen Rothwell
2012-10-02 12:26 ` Chris Mason [this message]
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=20121002122653.GB1140@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.