From: C Anthony Risinger <anthony@extof.me>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Chris Mason <chris.mason@oracle.com>,
Mitch Harder <mitch.harder@sabayonlinux.org>,
linux-btrfs@vger.kernel.org
Subject: Re: [GIT PULL][PATCH v2 0/6] btrfs: Add lzo compression support
Date: Tue, 30 Nov 2010 11:12:17 -0600 [thread overview]
Message-ID: <AANLkTimcGV1GdPZcuya3MwFbkkhwRyj5MdEvY1fAmCWu@mail.gmail.com> (raw)
In-Reply-To: <4CF44C95.6020908@cn.fujitsu.com>
On Mon, Nov 29, 2010 at 7:00 PM, Li Zefan <lizf@cn.fujitsu.com> wrote:
> C Anthony Risinger wrote:
>> On Wed, Nov 17, 2010 at 8:08 PM, Li Zefan <lizf@cn.fujitsu.com> wrot=
e:
>>>
>>> You can pull from:
>>>
>>> =A0 =A0 =A0 =A0git://repo.or.cz/linux-btrfs-devel.git lzo-support
>>>
>>>
>>> Lzo is a much faster compression algorithm than gzib, so would allo=
w
>>> more users to enable transparent compression, and some users can
>>> choose from compression ratio and compression speed.
>>
>> is this in a branch somewhere? =A0or for inclusion in .37/.38? =A0th=
is is
>> a very attractive feature.
>>
>> what's the proper place (repo/branch) to see what is pending?
>
> As a new feature, it's too late for .37. Hope to see it merged in .38
> merge window.
:-(
yeah i thought it was already too late for .37, but i'd love to see
this for .38... should add even more kick to my eee s101 netbook.
> Chris' btrfs-unstable git tree is the "official" place to see what is
> pending, but just he hasn't picked up those patches, so for now it
> only sits in my own tree.
i knew about Chris' tree, i probably should have been more clear;
instead of "pending" i should have said "awaiting review", ie. is
there a repo Chris or someone else keeps with all the potential
patches (such as this, or the recent readonly ones, etc.)?
i keep a pretty good eye on the list, but i thought maybe someone
already had a nice central point to see these "up and coming" patches
that aren't necessarily "pending" for mainline yet.
thanks Li,
C Anthony
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-11-30 17:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 2:08 [GIT PULL][PATCH v2 0/6] btrfs: Add lzo compression support Li Zefan
2010-11-18 2:09 ` [PATCH v2 1/6] btrfs: Fix bugs in zlib workspace Li Zefan
2010-11-18 2:10 ` [PATCH v2 2/6] btrfs: Fix error handling in zlib Li Zefan
2010-11-18 2:10 ` [PATCH v2 3/6] btrfs: Allow to add new compression algorithm Li Zefan
2010-11-18 2:10 ` [PATCH v2 4/6] btrfs: Add lzo compression support Li Zefan
2010-11-18 2:11 ` [PATCH v2 5/6] btrfs: Allow to specify compress method when defrag Li Zefan
2010-11-18 2:11 ` [PATCH v2 6/6] btrfs: Extract duplicate decompress code Li Zefan
2010-11-29 17:54 ` [GIT PULL][PATCH v2 0/6] btrfs: Add lzo compression support C Anthony Risinger
2010-11-30 1:00 ` Li Zefan
2010-11-30 17:12 ` C Anthony Risinger [this message]
2010-12-01 1:02 ` Li Zefan
2010-12-24 5:35 ` cwillu
2010-12-24 6:55 ` Li Zefan
2010-12-24 12:32 ` Chris Mason
2010-12-24 20:45 ` Chris Mason
2010-12-26 3:31 ` C Anthony Risinger
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=AANLkTimcGV1GdPZcuya3MwFbkkhwRyj5MdEvY1fAmCWu@mail.gmail.com \
--to=anthony@extof.me \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mitch.harder@sabayonlinux.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).