Comment #1 on issue 2156 by [email protected]: lost commits
http://code.google.com/p/lilypond/issues/detail?id=2156
Hello,
I'm not sure about the 'approximately 10 commits' calculation - but of
course I am probably wrong - I downloaded staging-broken-dec-23, checked it
out, ran git log --pretty to a txt file going back to Mike's fix:
When he removed his accidental valgrind entry in one of the files
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=1665810dee903c597ecafdbf64461899141165f4
Then did the same for current master.
Took both files, removed the commit hashes and then ran it through sort and
uniq -u
With what was left; I then walked through manually removing all those
commit entries that are in current master and was left with 3 commits
"Build: Fix dependencies for translated manuals (issue 2125)."
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=dec9be69cd4fa39a469d16220781a6c0372ad7bf
Tracker Issue 2125
Rietveld Issue http://codereview.appspot.com/5494069
"Build: Unify the rules and variables for xref-map files."
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=01d0af4762f691d292587ca81d824bcdd0830bc6
Cannot find a tracker or Rietveld for this one.
and
"Build: Update timestamp when linking files."
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=3c7c453b1fa4604a02e28787777918a5ae3de4fa
Again I cannot find the tracker or Rietveld.
Hope this helps (at least for these 3 commits).
James
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
