Am 22.12.2013 12:06, schrieb David Kastrup:
Urs Liska <u...@openlilylib.org> writes:
Am 22.12.2013 10:54, schrieb David Kastrup:
I see that you used @code{vi} and @code{git-cl} rather than @command{vi}
and @command{git-cl}: any particular reason for that?
I was suggested to use that on Rietveld.
So, no, no particular reason.
Yes, I know: I'm not exactly being timely in bringing up issues. Sorry
for that.
As I'm still working on it with the make doc issue I can also fix that
myself and resend a new patch.
As you prefer.
Attached is an updated patch using @command instead of @code.
Rebased patch passes make doc (issues in other subthread solved).
Thanks for pushing
Urs
>From b653da284971802af8dc955b94ed1dbcddda18e9 Mon Sep 17 00:00:00 2001
From: Urs Liska <g...@ursliska.de>
Date: Thu, 12 Dec 2013 12:06:39 +0100
Subject: [PATCH] Issue 3719: CG: Add comment about git-cl editor
git-cl fires either the editor specified by the
EDITOR environment variable or vi if EDITOR isn't defined.
Commit mentions this in the CG
---
Documentation/contributor/source-code.itexi | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/contributor/source-code.itexi b/Documentation/contributor/source-code.itexi
index f44dd31..5a742a1 100644
--- a/Documentation/contributor/source-code.itexi
+++ b/Documentation/contributor/source-code.itexi
@@ -1384,6 +1384,11 @@ can be used.
@end itemize
+First you will see a terminal editor where you can edit the
+message that will accompany your patch. @command{git-cl} will respect
+the @command{EDITOR} environment variable if defined, otherwise it
+will use @code{vi} as the default editor.
+
After prompting for your Google email address and password, the
patch set will be posted to Rietveld, and you will be given a URL
for your patch.
--
1.7.10.4
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
