Erik Sandberg writes: > I finally got CVS to work. So I'll soon upload the bug database to CVS. I > think I will create a separate branch lilypond_2_2 for bugs in that version.
Ok. > 1. What is the easiest way of invoking lilypond directly from the > source tree? See http://mail.gnu.org/archive/html/bug-lilypond/2004-04/msg00039.html > 2. I'm about to create the new branch now. I don't want to screw anything up, > so can somebody please verify that the following command line is what I > should do? > ~/lily-bugs$ cvs -z3 -d [EMAIL PROTECTED]:/cvsroot/lilypond import > lily-bugs 1.1.1 lilypond_2_2 CVS has a marvellously clumsy interface, but I'm pretty sure that this won't create a lilypond_2_2 branch, lilypond_2_2 here is the vendor tag. Although it seems to be possible with import -b; I'd suggest to create the module first: ~/lily-bugs-TRUNK$ cvs -z3 -d [EMAIL PROTECTED]:/cvsroot/lilypond import lily-bugs 1.1.1 erik and then create the branch: cd .. cvs -d ... co lily-bugs cd lily-bugs cvs tag -b lilypond_2_2 cvs update -r lilypond_2_2 <add files> etc. > (I beleive that this would create a new module lily-bugs under > /cvsroot/lilypond, containing all files in the current working > directory.. is this true?) Yes. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org _______________________________________________ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
