Do we need a separate branch (or even repository) for web/ stuff? I propose that we merge this with the main branch.
PRO: + one less branch/repo to track + easier to fix typos in the web pages + we can direct everybody to look at the CG (no more README in the newweb/ branch) + allows better integration with the other docs (this is more a post-GOP feature) CON: - adds 30 megs to the main branch (including the .git dir) - makes translations harder? (maybe? ... I don't know if this is true, but IMO this is the only real reason to avoid doing this) If we agree with this proposal, then we'll be left with: lilypond repo . master branch . individual testing branches . archive branches of old stables . translation branch gub repo . master Cheers, - Graham _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
