From: Zach Brown <zab@zabbo.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Marcus Meissner <Marcus.Meissner@caldera.de>,
linux-kernel@vger.kernel.org
Subject: Re: PATCH: maestro ported to 2.4 PCI API
Date: Mon, 21 May 2001 16:31:44 -0400 [thread overview]
Message-ID: <20010521163144.A9581@erasmus.off.net> (raw)
In-Reply-To: <20010521144554.C7003@erasmus.off.net> <E151uhF-0000hs-00@the-village.bc.nu>
In-Reply-To: <E151uhF-0000hs-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, May 21, 2001 at 07:46:25PM +0100
> Its useful to have version ids. So it would be better people used them more
I wasn't sure, so am happy leaving them in as well :)
I suppose they're an easier way to sync dmesg with code version than
knowing what is in which kernel version.
--
zach
prev parent reply other threads:[~2001-05-21 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-21 15:37 PATCH: maestro ported to 2.4 PCI API Marcus Meissner
2001-05-21 17:05 ` Francois Romieu
2001-05-21 21:23 ` Marcus Meissner
2001-05-21 18:45 ` Zach Brown
2001-05-21 18:46 ` Alan Cox
2001-05-21 20:31 ` Zach Brown [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=20010521163144.A9581@erasmus.off.net \
--to=zab@zabbo.net \
--cc=Marcus.Meissner@caldera.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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