From: "Amir G." <amir73il@users.sourceforge.net>
To: Andreas Dilger <adilger@dilger.ca>
Cc: "linux-ext4@vger.kernel.org development"
<linux-ext4@vger.kernel.org>, Theodore Tso <tytso@mit.edu>
Subject: Re: [PATCH 1/8] e2fsprogs: Next3 on-disk format changes
Date: Wed, 23 Jun 2010 07:16:16 +0300 [thread overview]
Message-ID: <AANLkTikVckjeT6FBClcd8ogKoxt50T8oGw-FfpEa1eik@mail.gmail.com> (raw)
In-Reply-To: <993280B6-32DB-4ABC-86B6-0CFCA9BECCFD@dilger.ca>
On Tue, Jun 22, 2010 at 7:21 PM, Andreas Dilger wrote:
>
> It would have been good to have this discussion on the list, since I didn't see any replies to your patches and assumed nobody had taken the time to look at them.
>
> It wouldn't be a terrible idea to post the new patches to the list, if you aren't still in the middle of updating them.
>
Actually, I don't know of anyone who did look at the patches besides
Ted and as far as I know,
he only looked at the first patch (on-disk format changes) because I
have asked him to approve the changes.
The discussion about the on-disk format was going on in another thread:
http://marc.info/?l=linux-ext4&m=127393198501070&w=2
And finally, Ted has approved these changes:
http://marc.info/?l=linux-ext4&m=127611066022974&w=2
I will try to re-post the patches next week.
Mind you, these are only 8 small patches for e2fsprogs.
There are also 40 bigger patches for Next3 itself (available on download page).
Would you like me to post those as well?
Thanks,
Amir.
next prev parent reply other threads:[~2010-06-23 4:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 18:32 [PATCH 1/8] e2fsprogs: Next3 on-disk format changes Andreas Dilger
2010-06-22 9:47 ` Amir G.
[not found] ` <993280B6-32DB-4ABC-86B6-0CFCA9BECCFD@dilger.ca>
2010-06-23 4:16 ` Amir G. [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-05 18:28 [PATCHSET] e2fsprogs: Next3 patch series Amir Goldstein
2010-05-05 18:28 ` [PATCH 1/8] e2fsprogs: Next3 on-disk format changes Amir Goldstein
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=AANLkTikVckjeT6FBClcd8ogKoxt50T8oGw-FfpEa1eik@mail.gmail.com \
--to=amir73il@users.sourceforge.net \
--cc=adilger@dilger.ca \
--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).