From: Gene Czarcinski <gene@czarc.net>
To: dsterba@suse.cz
Cc: chris.mason@fusionio.com, linux-btrfs@vger.kernel.org,
josef@toxicpanda.com
Subject: Re: [GIT PULL] btrfs-progs: more bugfixes for 0.20-rc1
Date: Fri, 18 Jan 2013 16:02:09 -0500 [thread overview]
Message-ID: <50F9B851.1020908@czarc.net> (raw)
In-Reply-To: <20130118172226.GC19967@twin.jikos.cz>
On 01/18/2013 12:22 PM, David Sterba wrote:
> On Fri, Jan 18, 2013 at 10:33:18AM -0500, Gene Czarcinski wrote:
>> I would like to recommend some additional patches for inclusion since they
>> are currently part of the Fedora 18 btrfs-tools package.
> Thanks. For now I'd like to gather all the small bugfixes and updates
> that are likely not to create any significant conflicts with whatever
> Chris has in his tree and skip new features, UI changes or non-obvious
> fixes.
>
>> Josef Bacik: detect if the disk we are formatting is a ssd V2
>> http://article.gmane.org/gmane.comp.file-systems.btrfs/18749
> This is IMO a safe feature, the comments were addressed in the final
> patch so we can try to push it.
>
>> This one may be a little more of a problem since the suggested man update is
>> missing and there is a second part for the kernel (status unknown).
>> Josef Bacik: add btrfs device ready command
>> http://article.gmane.org/gmane.comp.file-systems.btrfs/18129
>> Since Fedora uses a "stock" a kernel as possible, I suspect the
>> corresponding patch is applied.
> The kernel part of 'device ready' was merged to 3.6.
>
>> There are two or three other patches that appear to make sense but I have no
>> idea if they have been submitted.
> Please send them to the list.
>
Josef Bacik <josef@toxicpanda.com> is the current Fedora maintainer as
indicated in bugzilla.
<mailto:josef@toxicpanda.com>
Currently in Fedora 18, btrfs-progs is the "v0.20-rc1 with git commit id
<mailto:josef@toxicpanda.com>91d9eec" plus a total of seven patches.
Two of those patches from the list which I have already indicated. The
rest of those patches have been around for a while (at least since mid
2011) and I cannot find any doc.
While I could send them in (and will if needed), I feel a little uneasy
since Josef is responsible in Fedora. While this may be a different
individual since the email address is different, I suspect this Josef is
the same Josef who wrote the other two patches and he may be able to
speak to them better.
I have been scraping mailing list for all of the btrfs-progs patches and
plan to gradually test them. Since it appears you will be doing
something similar, if you want to point me to some for testing, I will
give it a shot with some virtual and some real-iron testing. And
sometimes it is also a matter of the time needed to refit/rebase patches.
Gene
next prev parent reply other threads:[~2013-01-18 21:02 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
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 [this message]
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=50F9B851.1020908@czarc.net \
--to=gene@czarc.net \
--cc=chris.mason@fusionio.com \
--cc=dsterba@suse.cz \
--cc=josef@toxicpanda.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.