***snip "do we actually want a separate 'For unix developers' "
discussion about the new CG 1 introduction ***
I'm not happy with the current layout in having it as a node. If we
have it at all, I'd suggest a small bit at the top of the "for other
contributors" section. Mark, what do you think about this patch?
Cheers,
- Graham
From f45b650b077e61b32ece725cd2177c619535d95c Mon Sep 17 00:00:00 2001
From: Graham Percival <gra...@percival-music.ca>
Date: Fri, 8 Jan 2010 15:11:02 +0000
Subject: [PATCH] Doc: CG: merge two "for XYZ contributors" together.
---
Documentation/contributor/introduction.itexi | 29 +++++++++-----------------
1 files changed, 10 insertions(+), 19 deletions(-)
diff --git a/Documentation/contributor/introduction.itexi b/Documentation/contributor/introduction.itexi
index 7a1f586..94c9608 100644
--- a/Documentation/contributor/introduction.itexi
+++ b/Documentation/contributor/introduction.itexi
@@ -3,11 +3,11 @@
@node Introduction to contributing
@chapter Introduction to contributing
+FIXME add fluff.
@menu
* Overview of tasks::
-* For unix developers::
-* For other contributors::
+* Summary of contributing::
* Mentors::
@end menu
@@ -21,26 +21,17 @@ quite possibly as the very first thing. This requires having a
macro for it, which depends on issue 939.
-...@node For unix developers
-...@section For unix developers
+...@node Summary of contributing
+...@section Summary of contributing
+...@cartouche
-To download the LilyPond Git repository:
-
-...@example
-git clone git://git.sv.gnu.org/lilypond.git
-...@end example
-
-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.
-
-
-...@node For other contributors
-...@section For other contributors
+...@strong{ultra-fast summary for Unix developers}: source code is at
+...@code{git://git.sv.gnu.org/lilypond.git}. Documentation is built
+with Texinfo, after pre-processing with @code{lilypond-book}.
+Send well-formed patches to @email{lilypond-devel@@gnu.org}.
+...@end cartouche
The LilyPond source code is maintained as a Git repository, which
contains:
--
1.6.0.4
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
