From: Chris Mason <chris.mason@oracle.com>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [GIT PULL] ENOSPC rework and random fixes for next merge window
Date: Wed, 28 Sep 2011 07:58:17 -0400 [thread overview]
Message-ID: <1317211065-sup-2064@shiny> (raw)
In-Reply-To: <1317072992-28375-1-git-send-email-josef@redhat.com>
Excerpts from Josef Bacik's message of 2011-09-26 17:36:32 -0400:
> Hello,
>
> Chris can you pull from
>
> git://github.com/josefbacik/linux.git for-chris
I've pulled this into a new integration-test branch where I'm starting
to pile things in for the next merge window. Thanks Josef!
-chris
prev parent reply other threads:[~2011-09-28 11:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 21:36 [GIT PULL] ENOSPC rework and random fixes for next merge window Josef Bacik
2011-09-27 15:01 ` David Sterba
2011-09-27 15:11 ` Josef Bacik
2011-09-28 11:58 ` 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=1317211065-sup-2064@shiny \
--to=chris.mason@oracle.com \
--cc=josef@redhat.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;
as well as URLs for NNTP newsgroup(s).