From: Johannes Gilger <heipei@hackvalue.de>
To: Git Mailing List <git@vger.kernel.org>
Cc: Johannes Gilger <heipei@hackvalue.de>
Subject: [PATCH] git-commit: Only describe --dry-run once
Date: Sun, 13 Sep 2009 15:35:05 +0200 [thread overview]
Message-ID: <1252848905-19115-1-git-send-email-heipei@hackvalue.de> (raw)
Junio described the option in 3a5d13a and then again in 60c2993.
Also fix a small typo in the documentation for git-clone.
Signed-off-by: Johannes Gilger <heipei@hackvalue.de>
---
Documentation/git-clone.txt | 2 +-
Documentation/git-commit.txt | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
index f23100e..aacf4fd 100644
--- a/Documentation/git-clone.txt
+++ b/Documentation/git-clone.txt
@@ -130,7 +130,7 @@ objects from the source repository into a pack in the cloned repository.
--branch <name>::
-b <name>::
Instead of pointing the newly created HEAD to the branch pointed
- to by the cloned repositoroy's HEAD, point to <name> branch
+ to by the cloned repository's HEAD, point to <name> branch
instead. In a non-bare repository, this is the branch that will
be checked out.
diff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt
index 64f94cf..b2817b4 100644
--- a/Documentation/git-commit.txt
+++ b/Documentation/git-commit.txt
@@ -8,7 +8,7 @@ git-commit - Record changes to the repository
SYNOPSIS
--------
[verse]
-'git commit' [-a | --interactive] [-s] [-v] [-u<mode>] [--amend] [--dry-run]
+'git commit' [-a | --interactive] [-s] [-v] [-u<mode>] [--amend]
[(-c | -C) <commit>] [-F <file> | -m <msg>] [--dry-run]
[--allow-empty] [--no-verify] [-e] [--author=<author>]
[--cleanup=<mode>] [--] [[-i | -o ]<file>...]
--
1.6.5.rc1
next reply other threads:[~2009-09-13 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-13 13:35 Johannes Gilger [this message]
2009-09-13 18:53 ` [PATCH] git-commit: Only describe --dry-run once Junio C Hamano
2009-09-13 19:25 ` Johannes Gilger
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=1252848905-19115-1-git-send-email-heipei@hackvalue.de \
--to=heipei@hackvalue.de \
--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).