Hi Tassilo, Thanks *very* much for the information! That's really very useful to me.
Cheers, Chris On 14 Jun 2012, at 12:45, Tassilo Horn wrote: > Tassilo Horn <tass...@member.fsf.org> writes: > >> Check out http://www.gnu.org/licenses/gpl-howto.html >> >> That says that you should add at least a copyright notice and >> statement of copying permission. Fiddeling with the history of each >> and every source file sounds a bit awkward. Maybe you could ask the >> folks at licens...@fsf.org for advice. > > The question was very interesting, so I asked the guys on #gnu. I was > told that a lack of license and copyright information basically means: > you are not allowed to do anything with the code, well, except for > looking at it if its on some public hosting site. > > So you should be safe to add copyright and licensing information with a > new commit, and nobody will be legally allowed to build a nuclear rocket > steering system from some older revision. > > Bye, > Tassilo > > -- > You received this message because you are subscribed to the Google Groups > "Git for human beings" group. > To post to this group, send email to git-users@googlegroups.com. > To unsubscribe from this group, send email to > git-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/git-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
