Hmm... there is some misunderstanding here, see:
> I got bored of libc2 a while back. I prefer change
Now, what would you think if you developed libc2 and were about to go
to libc3 and then some company took libc2 made their own libc3 which is
incompatible to the libc3 that has been publicly announced some time ago,
put *your* address into the bug-report address if *their* libc3, told the
public nothing about the highly experimental aspect of their libc3 (that
will certainly not be compatible to the "official" libc3) etc.. etc...
I certainly am not "never change anything", I wouldn't have tried to patch
that pgcc thingy if I were. I am against mindless forking without stating
this, though, even if allowed by the license.
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@opengroup.org |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/