From: Davidlohr Bueso <dave@gnu.org>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux-ng <util-linux-ng@vger.kernel.org>
Subject: Re: [PATCH 3/3] mkfs.minix: add support for minix3 fs
Date: Wed, 06 Apr 2011 11:22:40 -0300 [thread overview]
Message-ID: <1302099760.2142.3.camel@offworld> (raw)
In-Reply-To: <20110406083627.GA6491@nb.net.home>
On Wed, 2011-04-06 at 10:36 +0200, Karel Zak wrote:
> On Thu, Mar 31, 2011 at 11:59:38AM -0300, Davidlohr Bueso wrote:
> > #define INODE_SIZE (sizeof(struct minix_inode))
...
>
> Oh.. Davidlohr, you forgot regression test ;-) What about to add
>
> mkfs.minix -{1,2,3}
>
> to tests/ts/minix/mkfs{1,2,3} ?
>
> It would be also nice to add MINIX3_SUPER_MAGIC to fsck.minix and
> print a warning that v3 is unsupported (yet?).
I had a feeling you would dislike the sloppy code (which was already a
part of mkfs.minix), so heck, let's invade it massively, like partx.
Like you mention, we need to go through several patches, which I will be
sending you over the next few days, this way it might be a bit easier to
merge.
Thanks,
Davidlohr
prev parent reply other threads:[~2011-04-06 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 14:59 [PATCH 3/3] mkfs.minix: add support for minix3 fs Davidlohr Bueso
[not found] ` <20110406083627.GA6491@nb.net.home>
2011-04-06 14:22 ` Davidlohr Bueso [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=1302099760.2142.3.camel@offworld \
--to=dave@gnu.org \
--cc=kzak@redhat.com \
--cc=util-linux-ng@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox