From: Ralf Baechle <ralf@linux-mips.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org, Florian Fainelli <florian@openwrt.org>
Subject: Re: [ATA] Rename routerboard 500 to 532
Date: Mon, 28 Apr 2008 12:47:30 +0100 [thread overview]
Message-ID: <20080428114730.GA7591@linux-mips.org> (raw)
In-Reply-To: <20080428114136.GA4766@linux-mips.org>
On Mon, Apr 28, 2008 at 12:41:36PM +0100, Ralf Baechle wrote:
> From: Ralf Baechle <ralf@linux-mips.org>
> Date: Mon, 28 Apr 2008 12:41:36 +0100
> To: Jeff Garzik <jeff@garzik.org>
> Cc: linux-ide@vger.kernel.org,
> Gabor Juhos <juhosgatopenwrt.org@linux-mips.org>,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
And that sort of crap happens if people put their email address in
anti-spam disguised form into the code, grrr...
Ralf
next prev parent reply other threads:[~2008-04-28 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 11:41 [ATA] Rename routerboard 500 to 532 Ralf Baechle
2008-04-28 11:47 ` Ralf Baechle [this message]
2008-04-29 6:18 ` Jeff Garzik
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=20080428114730.GA7591@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=florian@openwrt.org \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).