It is up to you. For large changes, it is convenient to have a separate branch, but it's also a good idea to have a topic branch, and prepare the changes there. Then, it is easier to make sure that only good changes get pushed into master.
2007/11/20, Graham Percival <[EMAIL PROTECTED]>: > Initially we wanted lilypond/gdp on a separate branch so that we could > tear apart the docs while keeping the 2.11 docs intact. But since we've > merged the docs now, is there actually any point in keeping them on a > separate branch? Would a separate branch just make more work for John, > for now real benefit? -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
