From: "David Byron" <dbyron@hheld.com>
To: "'Artem B. Bityutskiy'" <dedekind@yandex.ru>
Cc: linux-mtd@lists.infradead.org
Subject: RE: nandwrite in FAQ
Date: Wed, 2 Aug 2006 07:42:42 -0700 [thread overview]
Message-ID: <004801c6b641$e97c1330$c834800a@RudiDell> (raw)
In-Reply-To: AAAAAJOKoN+ryO5OkOyypB2eX+6kJyIA
On Tuesday August 1, 2006, Artem B. Bityutskiy wrote:
> MTD/JFFS2 FAQs are updated not very often. Feel free to
> send a patch - MTD's web contents are at
> git://git.infradead.org/mtd-www.git, GIT howto is at
> http://www.linux-mtd.infradead.org/doc/git.html.
I attached a patch to my original message. Is that enough? Getting an
account at infradead, making my own tree, etc. seems like overkill for a
three character change.
-DB
next reply other threads:[~2006-08-02 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 14:42 David Byron [this message]
2006-08-02 14:44 ` nandwrite in FAQ Artem B. Bityutskiy
2006-08-02 14:52 ` Artem B. Bityutskiy
-- strict thread matches above, loose matches on Subject: below --
2006-08-02 14:59 David Byron
2006-08-01 20:59 David Byron
2006-08-02 4:47 ` Artem B. Bityutskiy
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='004801c6b641$e97c1330$c834800a@RudiDell' \
--to=dbyron@hheld.com \
--cc=dedekind@yandex.ru \
--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