From: Nick Krause <xerofoify@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Work on ext4
Date: Fri, 25 Jul 2014 12:06:42 -0400 [thread overview]
Message-ID: <CAPDOMVihpeBwf=t_rWNSScOWNYero8cFy_+87ZGn7=7EXJk+QQ@mail.gmail.com> (raw)
In-Reply-To: <CAPDOMVjUZwkkgQLKctUUtPC5AmgPtbfXOheVdTvjcRk3T90HOQ@mail.gmail.com>
On Fri, Jul 25, 2014 at 11:59 AM, Nick Krause <xerofoify@gmail.com> wrote:
> On Fri, Jul 25, 2014 at 11:24 AM, Wang Shilong
> <wangshilong1991@gmail.com> wrote:
>> Hi Nick,
>>
>> Ext4 is relatively stable, i think there are a lot of things to do
>> for Btrfs development, maybe you can take a notice:
>>
>> https://btrfs.wiki.kernel.org/index.php/Main_Page
>>
>>
>>> Sorry about my other issues Ted. But if you would like to give
>>> me a change, I would like to help out on ext4 development.
>>> Just tell me what I should read before I start helping out:).
>>> Cheers Nick
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
> Thanks Wang,
> I will look into brtfs development later today.
> Cheers Nick
Hey Ted,
I will look into this later today.
Cheers Nick
prev parent reply other threads:[~2014-07-25 16:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 2:29 Work on ext4 Nick Krause
2014-07-25 14:59 ` Theodore Ts'o
2014-07-25 15:22 ` Nick Krause
2014-07-25 15:41 ` Theodore Ts'o
2014-07-25 16:07 ` Eric Sandeen
2014-07-28 4:01 ` Nick Krause
2014-07-28 12:45 ` Theodore Ts'o
2014-07-28 15:17 ` Nick Krause
2014-07-25 15:24 ` Wang Shilong
2014-07-25 15:59 ` Nick Krause
2014-07-25 16:06 ` Nick Krause [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='CAPDOMVihpeBwf=t_rWNSScOWNYero8cFy_+87ZGn7=7EXJk+QQ@mail.gmail.com' \
--to=xerofoify@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).