[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The worst that can happen to GPLed code
From: |
Per Abrahamsen |
Subject: |
Re: The worst that can happen to GPLed code |
Date: |
Tue, 15 Jun 2004 15:08:48 +0200 |
User-agent: |
Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (gnu/linux) |
Chris Jefferson <caj@cs.york.ac.uk> writes:
> However they do not have to make it clear in the normal
> execution of the binary that they have made any changes. This is in my
> opinion unacceptable if it's true.
For many free software projects, such notices IN THE NORMAL EXECUTION
of the binary would be prohibitive due to the number of people making
changes. Just look at the number of names in the contributers or
change log files for e.g. Emacs or GCC.
If you really feel you need such a requirement, I don't believe you
are ready to set your software free.
- Re: The worst that can happen to GPLed code, (continued)
- Re: The worst that can happen to GPLed code, John Hasler, 2004/06/29
- Re: The worst that can happen to GPLed code, Erik de Castro Lopo, 2004/06/29
- Re: The worst that can happen to GPLed code, Byron A Jeff, 2004/06/29
- Re: The worst that can happen to GPLed code, Per Abrahamsen, 2004/06/29
- Re: The worst that can happen to GPLed code, Tim Smith, 2004/06/29
- Re: The worst that can happen to GPLed code, Chris Jefferson, 2004/06/29
- Re: The worst that can happen to GPLed code, Barry Margolin, 2004/06/29
- Re: The worst that can happen to GPLed code, Stefaan A Eeckels, 2004/06/29
- Re: The worst that can happen to GPLed code, Paul Jarc, 2004/06/29
- Re: The worst that can happen to GPLed code, Barry Margolin, 2004/06/29
- Re: The worst that can happen to GPLed code, Paul Jarc, 2004/06/29
Re: The worst that can happen to GPLed code, Snuffelluffogus, 2004/06/29