This is the mail archive of the libc-hacker@sourceware.cygnus.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
From: Andreas Jaeger <aj@suse.de> Date: 24 Nov 1999 10:23:08 +0100 What can be done to improve the handling of patches? One solution would be to create a libc-patches list where everybody would send patches to (similar to gcc-patches). This way we could see what others have done, comment on the patches and don't duplicate the work.;-) I think this is a good idea, but the discussion on the patches should still happen on libc-hacker or libc-alpha. But still: * Nobody should work on larger changes (new functionality, major code reorganizations) without notifying the list first. * It's not always a bad thing that different people try to tackle the same problem. If they come out with the same solution, that probably means that the solution is right! If they don't come out with the same solution, this might indicate that some further investigation is necessary. Mark
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |