From: "Amir G." <amir73il@users.sourceforge.net>
To: Andi Kleen <andi@halobates.de>
Cc: Theodore Tso <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: Introducing Next3 - built-in snapshots support for Ext3
Date: Wed, 5 May 2010 03:03:05 +0200 [thread overview]
Message-ID: <q2x18730dc51005041803jf31e911et6a3e92b2be31e2f6@mail.gmail.com> (raw)
In-Reply-To: <87eihr4f24.fsf@basil.nowhere.org>
On Tue, May 4, 2010 at 9:55 PM, Andi Kleen wrote:
> "Amir G." writes:
>>
>> Since the snapshot support patches do not fall into standard patch
>> categories (feature/bug fix),
>
> What is it then?
It is in fact a rather big feature, that is, built-in snapshot support for Ext3.
However, since I did not expect such a big feature to be added to Ext3
in its current state of development,
I chose to introduce the feature as a new f/s which was branched from Ext3.
>
>> I would like to request your advise on the best way to move forward
>> with code review.
>
> The typical way to get code review is to post patches to the mailing
> list.
>
> However do it in smaller batches if you have a lot of them.
>
Very well, I will do that. I just figured there's not much sense in
reviewing the patches before
reading the basic design concepts in the wiki.
Thanks,
Amir.
next prev parent reply other threads:[~2010-05-05 1:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 15:41 Introducing Next3 - built-in snapshots support for Ext3 Amir G.
2010-05-03 9:47 ` Amir G.
2010-05-04 19:55 ` Andi Kleen
2010-05-05 1:03 ` Amir G. [this message]
2010-05-04 22:42 ` tytso
2010-05-05 2:05 ` Amir G.
2010-05-07 15:12 ` Andi Kleen
2010-05-07 19:22 ` Amir G.
2010-05-07 21:25 ` Ric Wheeler
2010-05-08 5:43 ` Amir G.
2010-05-08 11:48 ` Theodore Tso
2010-05-08 16:07 ` Amir G.
2010-05-08 17:25 ` tytso
2010-05-08 19:40 ` Amir G.
2010-05-09 2:25 ` Theodore Tso
2010-05-09 11:56 ` Amir G.
2010-05-15 6:14 ` Amir G.
2010-05-08 12:51 ` Ric Wheeler
2010-05-08 22:56 ` Amir G.
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=q2x18730dc51005041803jf31e911et6a3e92b2be31e2f6@mail.gmail.com \
--to=amir73il@users.sourceforge.net \
--cc=andi@halobates.de \
--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).