Yes, private is a state in between but not a result. I may want to have a "private" commit first before set it to public visible.
Christian Walter christian.walter@9elements.com 于 2021年11月12日周五 下午6:18写道：
Yeah - no.
The GPL allows you do keep your modifications private as long as you do not release them in any way. So if these private changes are not released somewhere they do not need to be public.
Chris
Am 12.11.2021 um 11:06 schrieb Keith Emery <k.emery.nbn@internode.on.net :
Your well within your rights not to. I don't believe anyone should be
compelled to expend effort for which they are not compensated.
But would anyone else like to explain why this isn't a GPL violation?
Because it really seems like it is.
On 12/11/21 8:44 pm, Patrick Georgi wrote: 12. November 2021 10:31, "Keith Emery" k.emery.nbn@internode.on.net
schrieb:
I'm fairly sure it say's 'you must publish the source code AND any
changes'. Did that change at some point?
I'm fairly sure that you don't understand the conditions under which
the GPL takes effect. Since I'm not your lawyer, I won't discuss this with you any further.
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org