Re: Kernel Firmware issue: are GPLed sourceless firmwares legal to distribute ?

with at least a colorable position, but not the one who added the sourceless code in the first place. Michael Poole -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Proposal: The DFSG do not require source code for data, including firmware

the project, are not necessarily so clear-cut about requiring a 3:1 supermajority. Michael Poole -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Proposal - Deferment of Changes from GR 2004-003

Guido Trotter writes: > This may be bad, since we've just changed the SC, and we actually don't > want to change it back. (It may be bad publicity too) > > Can't we have a GR that simply overrules aj's decision about his personal > interpretation of the SC (according to the constitution § 4.1.3)

Re: Proposal - Deferment of Changes from GR 2004-003

Guido Trotter writes: > This may be bad, since we've just changed the SC, and we actually don't > want to change it back. (It may be bad publicity too) > > Can't we have a GR that simply overrules aj's decision about his personal > interpretation of the SC (according to the constitution § 4.1.3) a

Re: Social Contract GR's Affect on sarge

verything that is in upstream documentation (but in a non-free format) will be an enormous amount of effort, especially as upstream adds new features. Michael Poole [1]- To forestall the suggestion to use valgrind instead, the program in question uses 500 MB of memory without any debugging overhead

Re: Social Contract GR's Affect on sarge

verything that is in upstream documentation (but in a non-free format) will be an enormous amount of effort, especially as upstream adds new features. Michael Poole [1]- To forestall the suggestion to use valgrind instead, the program in question uses 500 MB of memory without any debugging overhead