On Mon, Dec 28, 2009 at 6:22 PM, Mark Polesky <markpole...@yahoo.com> wrote: > You're proposing something like this? > > 1. Introduction to contributing > 2. Working with source code > 2.1 Using the `lilycontrib' GUI > 2.2 Getting source with Git > 2.2.1 [installing, configuring] > 2.2.2 [downloading LilyPond branches] > 2.3 Basic Git procedures > 2.4 Advanced Git procedures
Yeah. Ok, having 2.1 being one thing, and 2.2+ being another thing isn't precisely ideal, but it's clear enough. I mean, it'll be pretty obvious what the distinction is. >> I'm not entirely comfortable with documentation being >> "post-compile". How about having a "compiling" section >> (err, renamed to avoid a clash with the chapter name), >> with one subsection for "compiling the binary" and another >> for "compiling the documentation" ? > > Well, I thought `make doc' should always be preceded by > `make'. Am I wrong here? If you do "make EXTERNAL_BINARY doc", then you don't need "make" at all. Cheers, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
