From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: [RFC] scsi headers, in glibc-dev or linux-libc-headers-dev?
Date: Tue, 27 Apr 2010 12:14:34 +0200 [thread overview]
Message-ID: <hr6deb$dc1$1@dough.gmane.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Currently conflicting headers are both in glibc-dev and
linux-libc-headers-dev, which isn't a good thing. According to the
interwebs we should use the linux-libc-headers version.
Anyone opposed to removing the scsi headers from glibc? It would
basically involve reverting
http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=b8bb2a62b3916470c752bd79d31322b4358fc676
and
http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=83f41716ab6a2a9d83d4ff044dcef00595ecfeb2
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFL1rkKMkyGM64RGpERAuL4AJ9SNDjpJyCb2NMXbkHqTO61yUnFOQCdGud2
3sWfhdGpfGVfB7pQmiyekCk=
=ooCD
-----END PGP SIGNATURE-----
next reply other threads:[~2010-04-27 10:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 10:14 Koen Kooi [this message]
2010-04-27 18:21 ` [RFC] scsi headers, in glibc-dev or linux-libc-headers-dev? Tom Rini
2010-04-27 18:27 ` Tom Rini
2010-04-27 19:01 ` Koen Kooi
2010-04-27 19:34 ` Tom Rini
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='hr6deb$dc1$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.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.