From: Robert Millan <rmh@aybabtu.com>
To: grub-devel@gnu.org
Subject: linux headers
Date: Mon, 4 Jun 2007 18:59:30 +0200 [thread overview]
Message-ID: <20070604165930.GA17161@aragorn> (raw)
How is it that util/biosdisk.c makes effort to avoid including Linux headers
and defines Linux ioctl macros on its own?
This adds an extra maintainance burden, so I guess there must be a reason to do
it, but can't think of one..
--
Robert Millan
My spam trap is honeypot@aybabtu.com. Note: this address is only intended
for spam harvesters. Writing to it will get you added to my black list.
next reply other threads:[~2007-06-04 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 16:59 Robert Millan [this message]
2007-06-04 17:24 ` linux headers Robert Millan
2007-06-04 17:35 ` Jeroen Dekkers
-- strict thread matches above, loose matches on Subject: below --
2016-01-26 15:17 Linux headers Yegor Yefremov
2016-01-26 21:41 ` Sascha Hauer
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=20070604165930.GA17161@aragorn \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.