> The reason I added GPL is not because of some idea that this is allI don't know who told you that or why, but it's obvious nonsense, as this issue shows. Exports should be marked GPL if and only if they cannot be used except in a derivative work. If it is possible to use them without taking sufficient protectable expression, they should not be marked GPL. This was what everyone agreed to when GPL exports were created. DS --
| Sam Ravnborg | Are Section mismatches out of control? |
| Karl Meyer | PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out" |
| Bart Van Assche | Re: Is gcc thread-unsafe? |
| Adrian Bunk | Re: [Bug #10493] mips BCM47XX compile error |
git: | |
| Junio C Hamano | Re: [RFC/PATCH] git-branch: default to --track |
| Linus Torvalds | cleaner/better zlib sources? |
| Peter Stahlir | Git as a filesystem |
| Yossi Leybovich | corrupt object on git-gc |
| Manuel Wildauer | Re: Editing C with... |
| Mark Thomas | [i386/Thinkpad T41]USB mouse + Xorg obsd 4.1 |
| Stijn | Re: libiconv problem |
| Daniel Ouellet | Re: Router performance on OpenBSD and OpenBGPD |
| Felix Radensky | RE: e1000e "Detected Tx Unit Hang" |
| Johann Baudy | Packet mmap: TX RING and zero copy |
| David Miller | Re: 2.6.26/tg3 ping roundtrip times > 2000 ms on local network |
| Dushan Tcholich | Re: ksoftirqd high cpu load on kernels 2.6.24 to 2.6.27-rc1-mm1 |
