From: David Woodhouse <dwmw2@infradead.org>
To: "Brian J. Fox" <bfox@ua.com>
Cc: joern@wohnheim.fh-wedel.de, phil@river-bank.demon.co.uk,
hno@marasystems.com, linux-mtd@lists.infradead.org
Subject: Re: JFFS2 Format Documentation?
Date: Tue, 28 Jan 2003 14:12:56 +0000 [thread overview]
Message-ID: <12781.1043763176@passion.cambridge.redhat.com> (raw)
In-Reply-To: <E18dWJm-0000NO-00@speedy.datawave.net>
bfox@ua.com said:
> Perhaps he can't read that header file without "contaminating" his
> clean-room implementation?
I don't think we can argue that the node layout on the medium, as described
in that file, could possibly be considered sufficient to 'contaminate' an
alternative implementation.
--
dwmw2
next prev parent reply other threads:[~2003-01-28 13:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 9:56 JFFS2 Format Documentation? Phil Thompson
2003-01-28 11:10 ` Henrik Nordstrom
2003-01-28 12:35 ` Phil Thompson
2003-01-28 13:23 ` Jörn Engel
2003-01-28 13:44 ` David Woodhouse
2003-01-28 14:02 ` Brian J. Fox
2003-01-28 14:12 ` David Woodhouse [this message]
2003-01-28 14:11 ` Phil Thompson
2003-01-28 14:14 ` David Woodhouse
2003-01-28 16:13 ` Henrik Nordstrom
2003-01-28 16:26 ` David Woodhouse
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=12781.1043763176@passion.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=bfox@ua.com \
--cc=hno@marasystems.com \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-mtd@lists.infradead.org \
--cc=phil@river-bank.demon.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.