From: Artem Bityutskiy <dedekind@infradead.org>
To: Bruce_Leonard@selinc.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: Confused about how to make a UBIFS root filesystem
Date: Sat, 12 Apr 2008 12:02:19 +0300 [thread overview]
Message-ID: <1207990939.5965.96.camel@sauron> (raw)
In-Reply-To: <OF3C0A65DB.1AE994C5-ON88257428.00773679-88257428.00796BFD@selinc.com>
> This e-mail may contain SEL confidential information. The opinions
> expressed are not necessarily those of SEL. Any unauthorized disclosure,
> distribution or other use is prohibited. If you received this e-mail in
> error, please notify the sender, permanently delete it, and destroy any
> printout.
FYI, we usually do not like when people attach disclaimers like this to
mails they send to public mailing list for obvious reasons - it just
makes no sense.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2008-04-12 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 22:06 Confused about how to make a UBIFS root filesystem Bruce_Leonard
2008-04-12 9:00 ` Artem Bityutskiy
2008-04-12 11:22 ` Carl-Daniel Hailfinger
2008-04-12 9:02 ` Artem Bityutskiy [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=1207990939.5965.96.camel@sauron \
--to=dedekind@infradead.org \
--cc=Bruce_Leonard@selinc.com \
--cc=linux-mtd@lists.infradead.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