From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] silly dhcpd question
Date: Sat, 14 May 2005 15:11:36 -0400 [thread overview]
Message-ID: <5ba1d18ddcd32d92257d101620c273ac@plan9.bell-labs.com> (raw)
In-Reply-To: <200505141859.j4EIxr013451@demeter.cs.utwente.nl>
This is a good idea. I think I got all the places in the
kernel that print ethernet addresses. Really we should
use %E but I'm not sure why we don't.
Done.
Russ
next prev parent reply other threads:[~2005-05-14 19:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 21:59 Ronald G. Minnich
2005-05-13 22:04 ` "Nils O. Selåsdal"
2005-05-13 22:28 ` Ronald G. Minnich
2005-05-14 2:36 ` boyd, rounin
2005-05-14 5:44 ` lucio
2005-05-14 8:05 ` lucio
2005-05-14 8:38 ` andrey mirtchovski
2005-05-14 8:40 ` andrey mirtchovski
2005-05-14 16:18 ` Russ Cox
2005-05-14 16:31 ` boyd, rounin
2005-05-14 18:59 ` Axel Belinfante
2005-05-14 19:11 ` Russ Cox [this message]
2005-05-16 4:04 ` Ronald G. Minnich
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=5ba1d18ddcd32d92257d101620c273ac@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).