From 1bc77ba9a3e1ffc84af88eeff4ab8ad1a900ecf3 Mon Sep 17 00:00:00 2001 From: Mark Polesky Date: Thu, 7 Jan 2010 18:49:14 -0800 Subject: [PATCH] Doc: CG intro -- mention lily-git. --- Documentation/contributor/introduction.itexi | 31 ++++++++++++-------- 1 file changed, 18 insertions(+), 13 deletions(-) diff --git a/Documentation/contributor/introduction.itexi b/Documentation/contributor/introduction.itexi index a5bb2eab09..f239bd1bd4 100644 --- a/Documentation/contributor/introduction.itexi +++ b/Documentation/contributor/introduction.itexi @@ -33,8 +33,8 @@ git clone git://git.sv.gnu.org/lilypond.git Documentation is built using Texinfo. Subscribe to the developers' mailing list at @uref{http://lists.gnu.org/mailman/listinfo/lilypond-devel} and -send well-formed Git patches to @uref{mailto:lilypond-devel@@gnu.org} for -discussion. +send well-formed Git patches to +@uref{mailto:lilypond-devel@@gnu.org} for discussion. @node For other contributors @@ -55,7 +55,7 @@ since the program was born. The @q{official} LilyPond Git repository is hosted by the GNU Savannah software forge at @uref{http://git.sv.gnu.org}. -Although, since Git uses a @q{distributed} model, technically +Although, since Git uses a @emph{distributed} model, technically there is no central repository. Instead, each contributor keeps a complete copy of the entire repository (about 116M). @@ -65,14 +65,19 @@ is a simple text file generated by the @code{git} program that indicates what changes have been made (using a special format). If a contributor's patch is approved for inclusion (usually through the mailing list), someone on the current development team -will @emph{apply} (or @q{push}) the patch to the official -repository. - -Compiling (@q{building}) LilyPond allows developers to see how -changes to the source code affect the program itself. Compiling -is also needed to package the program for specific operating -systems or distributions. LilyPond can be compiled from a local -Git repository (for developers), or from a downloaded tarball (for -packagers). Compiling LilyPond is a rather involved process, and -most contributor tasks do not require it. +will @emph{push} the patch to the official repository. + +@emph{Compiling} (@q{building}) LilyPond allows developers to see +how changes to the source code affect the program itself. +Compiling is also needed to package the program for specific +operating systems or distributions. LilyPond can be compiled from +a local Git repository (for developers), or from a downloaded +tarball (for packagers). Compiling LilyPond is a rather involved +process, and most contributor tasks do not require it. + +Git is a complex and powerful tool, but tends to be confusing at +first, particularly for users not familiar with the command line +and/or version control systems. Contributors who don't want to +deal with Git directly are encouraged to use the +@command{lily-git} graphical user interface instead. -- 2.39.2