From: Greg Ungerer <gerg@snapgear.com>
To: linux-kernel@vger.kernel.org
Cc: dwmw2@infradead.org
Subject: Re: [2.5 patch] mics cleanups for mtd
Date: Sun, 19 Jan 2003 23:05:33 +1000 [thread overview]
Message-ID: <3E2AA29D.6070805@snapgear.com> (raw)
David Woodhouse <dwmw2@infradead.org> wrote:
> That's a reasonable idea, I suppose -- I haven't had someone bitch about
> me breaking the 2.2 uClinux build for a while now.
Hmmmm. There never was a 2.2 uClinux, we skipped 2.2.x all together.
Only 2.0.x and then 2.4.x, and now 2.5.x.
But I am sure some uClinux'er would have bitched about
breaking some version :-)
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Chief Software Wizard EMAIL: gerg@snapgear.com
Snapgear Pty Ltd PHONE: +61 7 3279 1822
825 Stanley St, FAX: +61 7 3279 1820
Woolloongabba, QLD, 4102, Australia WEB: www.SnapGear.com
next reply other threads:[~2003-01-19 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-19 13:05 Greg Ungerer [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-19 1:29 [2.5 patch] mics cleanups for mtd Adrian Bunk
2003-01-19 11:32 ` David Woodhouse
2003-01-19 11:56 ` Adrian Bunk
2003-01-20 8:18 ` David Woodhouse
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=3E2AA29D.6070805@snapgear.com \
--to=gerg@snapgear.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@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