Re: [Jamwiki-devel] git migration

[Thomas K. <th...@ko...>]

Hi Ryan, Peter,

thank you for your feedback. I also want to keep all history of all important 
files. Since I work with Git I often look in the log to see the commit that 
introduced some line of code. See also this recent video on this topic:
http://devblog.avdi.org/2012/06/22/use-revision-control-annotation-in-your-
editor/

So I care a lot about the full history of all java and other code files. But 
I'd strongly propose to remove all .jar files from the history. They don't 
help to understand the code and would only be needed in the very unlikely case 
that somebody would want to build a jamwiki version from 2007. And even for 
this case we could keep the SVN and take the jars from there.

Keeping the .jar files in the history would blow up the repository for 
everybody for the rest of the life of the jamwiki project without any benefit. 
Working with the repository only becomes slower.

I've pushed a new version with all tags and branches to
https://github.com/thkoch2001/jamwiki-wiki-conversion-wip2

I've only filtered the .jar files in this version. The history of the master 
branch is around 10MB. The additional history of the other branches is around 
9MB. Most of the other files that I deleted in the last version are in the 
dfisla branch.

I propose to review which branches we want to keep and to put the rest in some 
dark hidden corner of the internet.

You can do selective clones to get only one branch with the --branch and --
single-branch options of git clone.

Regards,

Thomas Koch, http://www.koch.ro