[zingermc]

If you still have the SVN repo, there should be a way to actually import all the commits to a Git repo (git-svn). Then, you could rebase the entire master branch of the current GitHub repo. That might show more of your contributions if many of them are hidden by the "guake_root" commit.

[felipelemos]

The SVN repository still exist with all its commits. Here it is the first SVN revision: https://sourceforge.net/p/guake-gnome-vte/code/1/

[VBprogrammer]

I only have a working knowledge of git but wouldn't that be equivalent to re-writing the whole history of the repo? Rebasing would give all of the commits a new commit ID and would cause conflicts everywhere.

Unless of course you just meant as an interesting way of being able to see the full history rather than suggesting the project adopt it.

[simcop2387]

Git has the ability to use grafts for this scenario. https://stackoverflow.com/questions/1220557/how-do-i-prepend...

[no_identd]

And if that's not enough, Eric S. Raymond has written a bunch of absurdly powerful tools for scenarios like this one:

http://www.catb.org/esr/reposurgeon/

https://gitlab.com/esr/git-debubble

https://gitlab.com/esr/git-weave

Some background information provided by ESR, in addition to what you can find on the homepage:

https://groups.google.com/forum/m/#!topic/golang-nuts/WstriK...

https://news.ycombinator.com/item?id=22304131