Graham Percival wrote:
On Fri, Feb 20, 2009 at 08:09:21AM -0600, Jonathan Kulp wrote:
Is this right? I surmise that this pulls down more code than strictly
necessary for working on docs, but I don't mind having the extra code.
Maybe I should delete the whole directory and do a fresh clone.
Oh, I forgot to mention...
I personally hope that you **don't** learn anything about git from
all this discussion. I need somebody who is intelligent, willing
to follow instructions, willing to patient while we work out
problems... but who fundamentally ONLY follows the instructions
written in the latest online version of CG 1.
That's the only way that we'll get good docs for new contributors.
Remember my "the only answer is RTFM" idea? i.e.
1. Contributor (you) has a problem.
2. Knowledgeable person glances at the docs, fixes / clarifies
the point in question.
3. Knowledgeable person says "RTFM 1.1 (but wait until midnight
when the new changes will be visilbe)"
4. Goto #1
5. Profit. ($$$)
Once we've gone through all this pain (you being confused about
git, and we (possibly including me) editing the CG), the next
contributor will have a much easier task.
Cheers,
- Graham
I'll try my best not to learn anything. :) I went and followed the
instructions in CG for creating the new branch and it worked fine, I
think. I got my "lastest" typo back anyway. So I fixed that and also
went through and made a bunch of quotation mark fixes to use the @q{}
and @qq{} command. I stripped trailing white spaces. My editor says
the line endings are unix. I hope it turns out o.k. on the other end.
Trevor, do you want to try applying this one? Thanks guys,
Jon
--
Jonathan Kulp
http://www.jonathankulp.com
>From 7c607e0fffafabe06c996aaecccbe6cab2988c4c Mon Sep 17 00:00:00 2001
From: Jonathan Kulp <j...@bashtop.(none)>
Date: Fri, 20 Feb 2009 08:53:42 -0600
Subject: [PATCH] Fix typo "lastest" to latest and numerous @q{} and @qq{} constructs.
---
Documentation/devel/git-starting.itexi | 46 ++++++++++++++++----------------
1 files changed, 23 insertions(+), 23 deletions(-)
diff --git a/Documentation/devel/git-starting.itexi b/Documentation/devel/git-starting.itexi
index dbef6f7..dc8b368 100644
--- a/Documentation/devel/git-starting.itexi
+++ b/Documentation/devel/git-starting.itexi
@@ -3,11 +3,11 @@
@chapter Starting with git
@menu
-* Getting the source code::
-* Updating the source code::
-* Sharing your changes::
-* Other interesting Git commands::
-* Git on Windows::
+* Getting the source code::
+* Updating the source code::
+* Sharing your changes::
+* Other interesting Git commands::
+* Git on Windows::
@end menu
@@ -15,13 +15,13 @@
@section Getting the source code
@menu
-* Git introduction::
-* Main source code::
-* Website source code::
-* Documentation translations source code::
-* Other branches::
-* Other locations for git::
-* Git user configuration::
+* Git introduction::
+* Main source code::
+* Website source code::
+* Documentation translations source code::
+* Other branches::
+* Other locations for git::
+* Git user configuration::
@end menu
@node Git introduction
@@ -86,7 +86,7 @@ you wish to do so, you will need more familiarity with git.
@item @code{gub}:
This stores the Grand Unified Binary, our cross-platform building
-tool.
+tool.
@c TODO: merge the gub stuff with this CG.
For more info, see @uref{http://lilypond.org/gub}. The git
location is:
@@ -138,10 +138,10 @@ git config --global user.email MYEMAIL@@EXAMPLE.NET
@section Updating the source code
@menu
-* Importance of updating::
-* Update command::
-* Resolving conflicts::
-* Technical notes::
+* Importance of updating::
+* Update command::
+* Resolving conflicts::
+* Technical notes::
@end menu
@@ -230,7 +230,7 @@ differ from origin/web. In this case, remember that other people
working like you on the remote web branch of
git://git.sv.gnu.org/lilypond.git/ know nothing about your own web
branch: this means that whenever you use a committish or make a patch,
-others expect you to take the lastest commit of origin/web branch as a
+others expect you to take the latest commit of origin/web branch as a
reference.
This README tries to explain most of Git commands needed for
@@ -248,8 +248,8 @@ Manual at
@section Sharing your changes
@menu
-* Producing a patch::
-* Committing directly::
+* Producing a patch::
+* Committing directly::
@end menu
@@ -261,7 +261,7 @@ changes meet the @ref{Code style} and/or @ref{Documentation
policy}, and checked that the entire thing compiles, you may
@example
-git commit -a
+git commit -a
git format-patch origin
@end example
@@ -295,8 +295,8 @@ git push
@section Other interesting Git commands
@menu
-* Git log::
-* Applying git patches::
+* Git log::
+* Applying git patches::
@end menu
--
1.5.4.3
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
