From: John Mandereau - LilyPond development <john.mandereau@gmail.com>
Date: Mon, 4 Jun 2012 11:21:29 +0000 (+0200)
Subject: Update lilypond-patchy-staging usage instructions
X-Git-Tag: release/2.15.40-1~4
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=3d3ce70b38cf37274abb8d226c8a41f30b83462a;p=lilypond.git

Update lilypond-patchy-staging usage instructions
---

diff --git a/Documentation/contributor/administration.itexi b/Documentation/contributor/administration.itexi
index 21fb76d2b7..1a75cc778a 100644
--- a/Documentation/contributor/administration.itexi
+++ b/Documentation/contributor/administration.itexi
@@ -188,15 +188,22 @@ export LILYPOND_GIT=~/lilypond-git
 then logging out and in.
 
 @item
-Run patchy once to set up config files.  Cancel this build
-(ctrl-c).
+Run patchy once to set up config files, answer @q{@code{n}} when it
+asks for going on, unless the default config file happens to suit your
+setup:
+@example
+cd PATH/TO/lilypond-extra.git/patches
+lilypond-patchy-staging.py
+@end example
+Following calls of @code{lilypond-patchy-staging.py} need not be made
+from the directory where it stands.
 
 @item
-Edit @file{$HOME/.lilypond-patchy-config} to provide working
-directories for your build directory, your results directory,
-compiler options and notification method.  If you don't want to
-use email notification, then delete everything after
-@code{smtp_command:}.
+Edit @file{$HOME/.lilypond-patchy-config} to provide the location of
+your local lilypond Git repository, working directories for your build
+directory, your results directory, compiler options and notification
+method.  If you don't want to use email notification, then delete
+everything after @code{smtp_command:}.
 
 @item
 Ensure that your new user has git push access.  Follow the
@@ -208,7 +215,7 @@ to run patchy unattended.
 
 @subheading lilypond-patchy-staging.py
 
-lilypond-patchy-staging.py is run with
+@code{lilypond-patchy-staging.py} is run with
 @example
 python lilypond-patchy-staging.py
 @end example