From: Thomas Schwinge <[EMAIL PROTECTED]>
I put this in.
Shall I keep sending messages like that one or do the people that are
interested read the commit-hurd mailing list?
I even did not know there was a commit-hurd mailing list :) I like to read
patches here.
Xavier
On Sun, Jan 22, 2006 at 10:57:30AM -0500, I wrote:
> > > [ NIC update patch ]
>
> It now finally found his way into CVS.
I took the time to document the new configure options that enable the new
drivers and committed that as well.
Regards,
Thomas
_
On Sun, 2006-01-22 at 17:06 +0100, Gianluca Guida wrote:
> Among lot of warning, while compiling GNU Mach with recent gcc's we
> get lot of warnings related to strict aliasing optimization. This
> might lead the compiler into producing incorrect code.
>
> I personally think that instead of modifyi
On Fri, Jan 20, 2006 at 11:45:09PM -0500, Marcus Brinkmann wrote:
> Just a general comment: If you commit a change, the date in the
> ChangeLog should be the date of the commit, not the date when the patch
> was written or submitted. I certainly didn't use to do it, so you will
> find wrong preced
Hi,
Among lot of warning, while compiling GNU Mach with recent gcc's we
get lot of warnings related to strict aliasing optimization. This
might lead the compiler into producing incorrect code.
I personally think that instead of modifying GNU Mach's code (and
limit our cast usage) we can simply g
On Sun, 2006-01-22 at 06:17 -0500, Thomas Schwinge wrote:
> On Fri, Jan 20, 2006 at 05:31:05AM -0500, I wrote:
> > 2005-11-05 Thomas Schwinge <[EMAIL PROTECTED]>
> >
> > * linux/src/drivers/net/ne2k-pci.c (ne_block_input, ne_block_output):
> > Fix previous patch.
>
> I put this in.
>
>
On Fri, Jan 20, 2006 at 05:31:05AM -0500, I wrote:
> 2005-11-05 Thomas Schwinge <[EMAIL PROTECTED]>
>
> * linux/src/drivers/net/ne2k-pci.c (ne_block_input, ne_block_output):
> Fix previous patch.
I put this in.
Shall I keep sending messages like that one or do the people that are
i