chrism0dwk <chrism0...@gmail.com> writes:
> I have been working for a couple of years on a scientific project in
> which I have kept my source code (C++) in a private Git repository on
> a private server. I am now at the stage where I would like to open
> source my code under GPLv3, and place it in a public repository (eg
> GitHub or GoogleCode). However, because the code has been private up
> to now, I have not bothered with adding the GPL to the source files.
> I'm worried about what this implies for a public repo -- I can add the
> GPL and commit, but this would not stop people from lifting the
> unlicensed code from previous commits.
> Is there anyway to fiddle the commits in a Git repository in order to
> add such a licence to the entire history?
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.
Of course, if you don't care about your project's history, you could
just add the headers now and copy all current files to the public
repository instead of pushing everything including the history via git.
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 email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at