From: Andrew Ruder <andy@aeruder.net>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: [PATCH 1/8] Removing -n option from git-diff-files documentation
Date: Fri, 27 Apr 2007 00:05:50 -0500 [thread overview]
Message-ID: <20070427050550.GA9594@bowser.ruder> (raw)
-n is not a short form of --no-index as the documentation
suggests. Removing it from the documentation and command
usage string.
Signed-off-by: Andrew Ruder <andy@aeruder.net>
---
Documentation/git-diff-files.txt | 4 ++--
builtin-diff-files.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-diff-files.txt b/Documentation/git-diff-files.txt
index b78c4c6..2e1e29e 100644
--- a/Documentation/git-diff-files.txt
+++ b/Documentation/git-diff-files.txt
@@ -8,7 +8,7 @@ git-diff-files - Compares files in the working tree and the index
SYNOPSIS
--------
-'git-diff-files' [-q] [-0|-1|-2|-3|-c|--cc|-n|--no-index] [<common diff options>] [<path>...]
+'git-diff-files' [-q] [-0|-1|-2|-3|-c|--cc|--no-index] [<common diff options>] [<path>...]
DESCRIPTION
-----------
@@ -36,7 +36,7 @@ omit diff output for unmerged entries and just show "Unmerged".
diff, similar to the way 'diff-tree' shows a merge
commit with these flags.
-\-n,\--no-index::
+--no-index::
Compare the two given files / directories.
-q::
diff --git a/builtin-diff-files.c b/builtin-diff-files.c
index 6ba5077..6cb30c8 100644
--- a/builtin-diff-files.c
+++ b/builtin-diff-files.c
@@ -10,7 +10,7 @@
#include "builtin.h"
static const char diff_files_usage[] =
-"git-diff-files [-q] [-0/-1/2/3 |-c|--cc|-n|--no-index] [<common diff options>] [<path>...]"
+"git-diff-files [-q] [-0/-1/2/3 |-c|--cc|--no-index] [<common diff options>] [<path>...]"
COMMON_DIFF_OPTIONS_HELP;
int cmd_diff_files(int argc, const char **argv, const char *prefix)
--
1.5.2.rc0.64.g8476
next reply other threads:[~2007-04-27 5:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 5:05 Andrew Ruder [this message]
2007-04-27 5:09 ` [PATCH 2/8] Document additional options for git-fetch Andrew Ruder
2007-04-27 5:09 ` [PATCH 3/8] Update git-fmt-merge documentation Andrew Ruder
2007-04-27 5:09 ` [PATCH 4/8] Update git-grep documentation Andrew Ruder
2007-04-27 5:09 ` [PATCH 5/8] Update -L documentation for git-blame/git-annotate Andrew Ruder
2007-04-27 5:09 ` [PATCH 6/8] Update git-http-push documentation Andrew Ruder
2007-04-27 5:09 ` [PATCH 7/8] Update git-local-fetch documentation Andrew Ruder
2007-04-27 5:10 ` [PATCH 8/8] Update git-http-fetch documentation Andrew Ruder
2007-04-27 18:05 ` [PATCH 1/8] Removing -n option from git-diff-files documentation Petr Baudis
2007-04-29 7:05 ` Junio C Hamano
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=20070427050550.GA9594@bowser.ruder \
--to=andy@aeruder.net \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).