From: "Brian J. Fox" <bfox@RoamingMessenger.com>
To: jasmine@regolith.co.uk
Cc: manningc2@actrix.gen.nz
Cc: linux-mtd@lists.infradead.org
Cc: panto@intracom.gr
Subject: Re: Cram FS on NAND - How to do this?
Date: Fri, 13 Jun 2003 09:45:31 -0700 [thread overview]
Message-ID: <E19QrgB-0003fC-00@speedy.datawave.net> (raw)
In-Reply-To: <Pine.LNX.4.53.0306131732140.12689@undine.linuxgrrls.org> (message from Jasmine Strong on Fri, 13 Jun 2003 17:33:07 +0100 (BST))
Date: Fri, 13 Jun 2003 17:33:07 +0100 (BST)
From: Jasmine Strong <jasmine@regolith.co.uk>
Cc: manningc2@actrix.gen.nz, panto@intracom.gr, linux-mtd@lists.infradead.org
On Fri, 13 Jun 2003, Brian J. Fox wrote:
> Why does the product have to remain nameless?
Because it's covered by a non-disclosure agreement until it is launched.
Okay. Please keep us posted -- this kind of adoption in the consumer
market is exactly the thing that is needed (for many reasons), and I'm
excited to hear about it.
Brian
--------------------------------------------------------------------
Brian J. Fox Roaming Messenger, Inc.
CTO www.RoamingMessenger.com
bfox@RoamingMessenger.com P:(805) 683-ROAM x119 F:(805) 964-6968
--------------------------------------------------------------------
prev parent reply other threads:[~2003-06-13 16:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 8:43 Cram FS on NAND - How to do this? Pantelis Antoniou
2003-06-11 8:51 ` David Woodhouse
2003-06-11 8:58 ` Pantelis Antoniou
2003-06-11 9:04 ` David Woodhouse
2003-06-11 9:10 ` Russ Dill
2003-06-11 9:12 ` David Woodhouse
2003-06-11 9:01 ` Jasmine Strong
2003-06-11 9:54 ` Pantelis Antoniou
2003-06-11 10:24 ` angainor
2003-06-11 19:22 ` Russ Dill
2003-06-12 8:22 ` Pantelis Antoniou
2003-06-12 9:06 ` Thomas Gleixner
2003-06-12 8:15 ` Pantelis Antoniou
2003-06-12 23:13 ` Charles Manning
2003-06-13 12:18 ` Jasmine Strong
2003-06-13 16:30 ` Brian J. Fox
2003-06-13 16:33 ` Jasmine Strong
2003-06-13 16:45 ` Brian J. Fox [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=E19QrgB-0003fC-00@speedy.datawave.net \
--to=bfox@roamingmessenger.com \
--cc=jasmine@regolith.co.uk \
--cc=manningc2@actrix.gen.nz \
/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