On 2013/12/09 09:31:57, hanwenn wrote:
also, for reviewing, you should do the file reorganization and the
code
reorganization in different changes.
It's also a good idea to move files and change files in different commits since git gets worse at tracking moves/renames the more changes happen in a single commit. While you can give git special command line options to make it more thorough, it's a pain to do this for the various tools and workflows somehow trying to reconstruct history. https://codereview.appspot.com/38530043/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
