Paul Eggert <[EMAIL PROTECTED]> writes:

> Simon Josefsson <[EMAIL PROTECTED]> writes:
>
>> +    * getpass.c: Add WIN32 implementation.  Conditionalize use of
>> +    termios.h, tcgetattr, tcsetattr and __fsetlocking.  Remove some
>> +    GLIBC specific code.
>
> Why remove the GLIBC specific code?  I'd rather keep gnulib in sync
> with glibc as much as possible.  I'm trying to get gnulib patches
> merged back into glibc.

The module isn't close to being in sync now.  Should I start with the
up-stream glibc code and add the necessary hacks to it to make it work
on non-GNU standards compliant POSIX, Windows, and uClibc instead?

The resulting code would look awful, and I think it would be weird to
have plenty of non-glibc specific hacks inside glibc.  But keeping
things in sync is a good idea, and I can work toward that goal for
this module if you want.

Thanks,
Simon


_______________________________________________
bug-gnulib mailing list
bug-gnulib@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnulib

Reply via email to