From: Brian Norris <computersforpeace@gmail.com>
To: Atlant Schmidt <aschmidt@dekaresearch.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Does UBI LEB-level access interlock happily with UBIfs access?
Date: Fri, 19 Sep 2014 10:06:52 -0700 [thread overview]
Message-ID: <20140919170652.GH1193@ld-irv-0074> (raw)
In-Reply-To: <0A40042D85E7C84DB443060EC44B3FD36D986A3009@dekaexchange07.deka.local>
On Tue, Sep 16, 2014 at 10:04:29AM -0400, Atlant Schmidt wrote:
> This e-mail and the information, including any attachments it
> contains, are intended to be a confidential communication only to the
> person or entity to whom it is addressed and may contain information
> that is privileged. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly prohibited.
> If you have received this communication in error, please immediately
> notify the sender and destroy the original message.
Can you please consider dropping this notice from your email? It's
effectively useless when you're sending mail to a publicly-accessible
(and indefinitely archived) mailing list.
Thanks,
Brian
prev parent reply other threads:[~2014-09-19 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 14:04 Does UBI LEB-level access interlock happily with UBIfs access? Atlant Schmidt
2014-09-19 15:27 ` Artem Bityutskiy
2014-09-19 16:58 ` Atlant Schmidt
2014-09-19 17:13 ` Artem Bityutskiy
2014-09-19 17:17 ` Atlant Schmidt
2014-09-19 17:24 ` Artem Bityutskiy
2014-09-20 12:54 ` Richard Weinberger
2014-09-22 8:34 ` Ricard Wanderlof
2014-09-22 8:42 ` Richard Weinberger
2014-09-19 17:06 ` Brian Norris [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=20140919170652.GH1193@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=aschmidt@dekaresearch.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