On Tue, Oct 28, 2008 at 01:33:35PM +0100, Jim Meyering wrote:
"Daniel P. Berrange" <berrange@redhat.com> wrote:
On Tue, Oct 28, 2008 at 12:21:25PM +0100, Jim Meyering wrote:
From: Jim Meyering <meyering@redhat.com>
Now, sys/socket.h is always available, and errno works.
With the removal of errno stuff and santization of headers I don't see all that much point in keeping socketcompat.h around at all - can't we just include the right things in the right places
Yes, of course. Actually, an earlier version did remove socketcompat.h, but that change was more invasive.
So how about if I remove socketcompat.h once these changes are committed?
Works for me Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|