2010/3/22 Jan Nieuwenhuizen <[email protected]>: > Hi, > > I've taken another look at fixing lily's history this weekend, > it should be ready now to replace our old broken repository,
Great! Thanks. Let's move. > Our current GIT archive suffers from major problems in the > CVS->GIT conversion, and also at the time of CVS conversion > (looong ago), Hopefully stats will improve from http://paconet.org/lilypond-statistics/files.html to something real. This deserves a new code_swarn video with the full history. > There's one small problem with replacing the old repository, > *all* committishes change, and everyone will have to make > a fresh clone, and any work based on the old repository > must be copied over to the new clone using git format-patch > and git am. My advice to translators is to keep the old repository until output of make-check is saved onto a file, and make two versions of it, coloured and no-color. Some diffs are not visible in coloured version. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
