From: Sean Estabrooks <seanlkml@sympatico.ca>
To: git@vger.kernel.org
Cc: Sean Estabrooks <seanlkml@sympatico.ca>
Subject: [PATCH] Fix trivial typo in git-log man page.
Date: Fri, 28 Apr 2006 09:15:03 -0400 [thread overview]
Message-ID: <BAYC1-PASMTP0933E0E4DDF253A9478776AEB20@CEZ.ICE> (raw)
Message-ID: <11462301062278-git-send-email-seanlkml@sympatico.ca> (raw)
Signed-off-by: Sean Estabrooks <seanlkml@sympatico.ca>
---
Documentation/git-log.txt | 7 +++----
1 files changed, 3 insertions(+), 4 deletions(-)
0afa7822c6a0d6ffa82f9d9b64c78df8587e190d
diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
index 76cb894..af378ff 100644
--- a/Documentation/git-log.txt
+++ b/Documentation/git-log.txt
@@ -14,13 +14,12 @@ DESCRIPTION
-----------
Shows the commit logs.
-The command takes options applicable to the gitlink::git-rev-list[1]
+The command takes options applicable to the gitlink:git-rev-list[1]
command to control what is shown and how, and options applicable to
-the gitlink::git-diff-tree[1] commands to control how the change
+the gitlink:git-diff-tree[1] commands to control how the change
each commit introduces are shown.
-This manual page describes only the most frequently used
-options.
+This manual page describes only the most frequently used options.
OPTIONS
--
1.3.1.gc672
next reply other threads:[~2006-04-28 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11462301062278-git-send-email-seanlkml@sympatico.ca>
2006-04-28 13:15 ` Sean Estabrooks [this message]
[not found] ` <11462301063885-git-send-email-seanlkml@sympatico.ca>
2006-04-28 13:15 ` [PATCH] Update the git-branch man page to include the "-r" option, Sean Estabrooks
[not found] ` <1146230106696-git-send-email-seanlkml@sympatico.ca>
2006-04-28 13:15 ` [PATCH] Fix up remaining man pages that use asciidoc "callouts" Sean Estabrooks
[not found] ` <11462301063607-git-send-email-seanlkml@sympatico.ca>
2006-04-28 13:15 ` [PATCH] Properly render asciidoc "callouts" in git man pages Sean Estabrooks
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=BAYC1-PASMTP0933E0E4DDF253A9478776AEB20@CEZ.ICE \
--to=seanlkml@sympatico.ca \
--cc=git@vger.kernel.org \
/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).