From: Goffredo Baroncelli <kreijack@gmail.com>
To: Chris Mason <chris.mason@fusionio.com>,
David Sterba <dsterba@suse.cz>,
Chris Mason <clmason@fusionio.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [GIT PULL] btrfs-progs: more bugfixes for 0.20-rc1
Date: Fri, 18 Jan 2013 18:32:10 +0100 [thread overview]
Message-ID: <50F9871A.90307@gmail.com> (raw)
In-Reply-To: <20130117175159.GA30656@shiny.int.fusionio.com>
Hi Chris,
On 01/17/2013 06:51 PM, Chris Mason wrote:
> On Thu, Jan 17, 2013 at 10:47:21AM -0700, David Sterba wrote:
>> Hi Chris,
>>
[...]
>
> Thanks Dave, pulling these in.
what about my patches "Enhance the command btrfs filesystem df" (see my
emails dated on 2012/11/02) [1] ?
You stated an interesting in these patches; however then I never heard
anything...
Do you want I resubmit ? I reached a general consensus ( == nobody was
too unsatisfied :-) ) about the wording and the format.
And I have another question: it is possible to access to the RAID5/6
develop branch. I am interesting to check how my patches work with
RAID5/6...
>
> -chris
BR
G.Baroncelli
[1] http://permalink.gmane.org/gmane.comp.file-systems.btrfs/21071
--
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2013-01-18 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 17:47 [GIT PULL] btrfs-progs: more bugfixes for 0.20-rc1 David Sterba
2013-01-17 17:51 ` Chris Mason
2013-01-18 17:32 ` Goffredo Baroncelli [this message]
2013-01-18 14:16 ` Gene Czarcinski
2013-01-18 14:44 ` David Sterba
2013-01-18 15:49 ` Gene Czarcinski
2013-01-18 15:55 ` Hugo Mills
2013-01-18 16:48 ` Gene Czarcinski
2013-01-18 15:33 ` Gene Czarcinski
2013-01-18 17:22 ` David Sterba
2013-01-18 21:02 ` Gene Czarcinski
2013-01-21 10:50 ` David Sterba
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=50F9871A.90307@gmail.com \
--to=kreijack@gmail.com \
--cc=chris.mason@fusionio.com \
--cc=clmason@fusionio.com \
--cc=dsterba@suse.cz \
--cc=kreijack@inwind.it \
--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.