From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>
Subject: [PATCH 1/2] gitcli: formatting fix
Date: Mon, 10 Sep 2012 12:53:59 -0700 [thread overview]
Message-ID: <1347306840-14007-1-git-send-email-gitster@pobox.com> (raw)
In-Reply-To: <7vhar5oemu.fsf@alter.siamese.dyndns.org>
The paragraph to encourage use of "--" in scripts belongs to the
bullet point that describes the behaviour for a command line without
the explicit "--" disambiguation, not a supporting explanation for
the entire bulletted list.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
Documentation/gitcli.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/gitcli.txt b/Documentation/gitcli.txt
index ea17f7a..c4edf04 100644
--- a/Documentation/gitcli.txt
+++ b/Documentation/gitcli.txt
@@ -37,7 +37,7 @@ arguments. Here are the rules:
file called HEAD in your work tree, `git diff HEAD` is ambiguous, and
you have to say either `git diff HEAD --` or `git diff -- HEAD` to
disambiguate.
-
++
When writing a script that is expected to handle random user-input, it is
a good practice to make it explicit which arguments are which by placing
disambiguating `--` at appropriate places.
--
1.7.12.322.g2c7d289
next prev parent reply other threads:[~2012-09-10 19:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 13:42 checkout extra files Angelo Borsotti
2012-09-03 13:55 ` Carlos Martín Nieto
[not found] ` <CAB9Jk9AkFW-fAqOZuhCMgMBdEZwDpe5ZG9Dkse=Wz_x9LvJEPw@mail.gmail.com>
2012-09-03 14:47 ` Carlos Martín Nieto
[not found] ` <CAB9Jk9BjO+HdxhaGxEyaDoXgGisi0QpuVvsx3dZUnJV1VoKN1g@mail.gmail.com>
2012-09-04 1:57 ` Carlos Martín Nieto
2012-09-03 13:59 ` Nguyen Thai Ngoc Duy
2012-09-03 19:36 ` Junio C Hamano
2012-09-04 1:49 ` Nguyen Thai Ngoc Duy
2012-09-04 2:55 ` Junio C Hamano
2012-09-04 7:15 ` Angelo Borsotti
2012-09-04 8:53 ` Junio C Hamano
2012-09-04 14:30 ` Junio C Hamano
2012-09-04 16:15 ` Junio C Hamano
2012-09-07 20:49 ` Junio C Hamano
[not found] ` <CAB9Jk9BtZzgi32kxVTbGC7eAjFG41bdae=MaK==sKq=9ohf8_w@mail.gmail.com>
2012-09-08 18:54 ` Junio C Hamano
2012-09-10 0:24 ` Junio C Hamano
2012-09-08 20:40 ` Philip Oakley
2012-09-09 3:31 ` Junio C Hamano
2012-09-09 13:48 ` Matthieu Moy
2012-09-09 18:23 ` Junio C Hamano
2012-09-09 23:25 ` Philip Oakley
2012-09-10 16:19 ` Jeff King
2012-09-10 17:09 ` Junio C Hamano
2012-09-10 17:19 ` Jeff King
2012-09-10 19:35 ` Junio C Hamano
2012-09-10 19:53 ` Junio C Hamano [this message]
2012-09-10 19:54 ` [PATCH 2/2] gitcli: contrast wildcard given to shell and to git Junio C Hamano
2012-09-10 20:11 ` checkout extra files Jeff King
2012-09-10 20:34 ` Junio C Hamano
2012-09-04 10:14 ` Nguyen Thai Ngoc Duy
[not found] ` <CAB9Jk9CNYr6LfWvyVqXvHjh7dzhUAuzkufqO9YMeOXg08D2cJw@mail.gmail.com>
[not found] ` <CACsJy8AUYigHVKjzE-0NT0hnOrQWdufN+COmkk=2Q8L1Rimytw@mail.gmail.com>
2012-09-04 13:24 ` Angelo Borsotti
2012-09-04 16:49 ` Junio C Hamano
2012-09-04 19:29 ` Angelo Borsotti
2012-09-04 20:44 ` Junio C Hamano
2012-09-04 22:53 ` Philip Oakley
2012-09-04 23:31 ` Junio C Hamano
2012-09-04 15:31 ` 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=1347306840-14007-1-git-send-email-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.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).