Le lundi 28 décembre 2009 à 21:18 +0000, Graham Percival a écrit : > I found the same problem with a fresh build, but then I remembered > that I'd switched back to 2.12.2 to build new regtests for the > comparison to 2.12.3. When I switched back to master after that, git > left some old files in my 2.13.10 tree. After doing a rm -rf * and > git reset --hard origin, the fresh build had no problems. > (why the mao would anybody want to check out a new branch while > leaving old files around?!)
Did git issue some warnings about left files when switching back to 2.13? Best, John
signature.asc
Description: Ceci est une partie de message numériquement signée
_______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel