From: Jonas Fonseca <fonseca@diku.dk>
To: Petr Baudis <pasky@ucw.cz>
Cc: git@vger.kernel.org
Subject: [PATCH] Cogito: Minor documentation fixes
Date: Fri, 23 Sep 2005 02:40:33 +0200 [thread overview]
Message-ID: <20050923004033.GA23708@diku.dk> (raw)
- Link to the new cg-object-id man page from cogito(7).
- Fix cg-help usage string listing in cogito(7).
- Make the cg-commit -m option more conforming to other options taking
arguments (the old usage remains).
- Use COMMIT_ID consistently.
Signed-of-by: Jonas Fonseca <fonseca@diku.dk>
---
Documentation/make-cogito-asciidoc | 4 ++--
cg-commit | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/make-cogito-asciidoc b/Documentation/make-cogito-asciidoc
--- a/Documentation/make-cogito-asciidoc
+++ b/Documentation/make-cogito-asciidoc
@@ -24,11 +24,11 @@ print_command_info()
echo
case "$cmdname" in
- cg-X*|*-id)
+ cg-X*)
echo "$cmdname::"
;;
cg-*)
- usage=$(sed -n '/^USAGE=/,0s/.*cg-[^ ]*\(.*\)"/\1/p' < $command)
+ usage=$(sed -n '/^USAGE=/,0s/.*"cg-[^ ]*\(.*\)"/\1/p' < $command)
echo "gitlink:$cmdname[] $usage::"
;;
esac
diff --git a/cg-commit b/cg-commit
--- a/cg-commit
+++ b/cg-commit
@@ -25,7 +25,7 @@
# Note, this is used internally by 'Cogito' when merging. This option
# does not make sense when files are given on the command line.
#
-# -mMESSAGE::
+# -m MESSAGE::
# Specify the commit message, which is used instead of starting
# up an editor (if the input is not `stdin`, the input is appended
# after all the '-m' messages). Multiple '-m' parameters are appended
@@ -111,7 +111,7 @@
# EDITOR::
# The editor used for entering revision log information.
-USAGE="cg-commit [-mMESSAGE]... [-C] [-e | -E] [-c COMMITID] [FILE]... [< MESSAGE]"
+USAGE="cg-commit [-m MESSAGE]... [-C] [-e | -E] [-c COMMIT_ID] [FILE]... [< MESSAGE]"
. ${COGITO_LIB}cg-Xlib || exit 1
--
Jonas Fonseca
reply other threads:[~2005-09-23 0:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050923004033.GA23708@diku.dk \
--to=fonseca@diku.dk \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).