From: Philip Oakley <philipoakley@iee.org>
To: GitList <git@vger.kernel.org>
Subject: [RFC/PATCH 2/2] doc: command line interface (cli) dot-repository dwimmery
Date: Sun, 19 May 2013 12:54:09 +0100 [thread overview]
Message-ID: <1368964449-2724-3-git-send-email-philipoakley@iee.org> (raw)
In-Reply-To: <1368964449-2724-1-git-send-email-philipoakley@iee.org>
The Git cli will generally accept dot '.' (period) as equivalent
to the current repository when appropriate. Tell the reader of this
'do what I mean' (dwim)mery action.
Signed-off-by: Philip Oakley <philipoakley@iee.org>
---
Documentation/gitcli.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/gitcli.txt b/Documentation/gitcli.txt
index 9ac5088..64bb386 100644
--- a/Documentation/gitcli.txt
+++ b/Documentation/gitcli.txt
@@ -59,6 +59,10 @@ working tree. After running `git add hello.c; rm hello.c`, you will _not_
see `hello.c` in your working tree with the former, but with the latter
you will.
+Just as, by convention, the filesystem '.' refers to the current directory,
+using a '.' (period) as a repository name in Git (a dot-repository) refers
+to your local repository.
+
Here are the rules regarding the "flags" that you should follow when you are
scripting Git:
--
1.8.1.msysgit.1
next prev parent reply other threads:[~2013-05-19 11:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-19 11:54 [RFC/PATCH 0/2] Extend dot repository documentation Philip Oakley
2013-05-19 11:54 ` [RFC/PATCH 1/2] config doc: add dot-repository note Philip Oakley
2013-05-19 17:43 ` Jonathan Nieder
2013-05-20 17:50 ` Junio C Hamano
2013-05-20 21:10 ` Philip Oakley
2013-05-19 11:54 ` Philip Oakley [this message]
2013-05-19 17:39 ` [RFC/PATCH 2/2] doc: command line interface (cli) dot-repository dwimmery Jonathan Nieder
2013-05-19 22:29 ` Philip Oakley
2013-05-20 17:55 ` Junio C Hamano
2013-05-20 21:09 ` Philip Oakley
2013-05-20 22:22 ` Junio C Hamano
2013-05-21 7:47 ` Philip Oakley
2013-05-21 16:23 ` Junio C Hamano
2013-05-21 21:21 ` Felipe Contreras
2013-05-21 22:33 ` Philip Oakley
2013-05-21 23:03 ` Felipe Contreras
2013-05-21 23:24 ` Junio C Hamano
2013-05-22 0:27 ` Felipe Contreras
2013-05-22 0:50 ` Junio C Hamano
2013-05-22 2:57 ` Felipe Contreras
2013-05-22 16:50 ` Junio C Hamano
2013-05-22 22:12 ` Felipe Contreras
2013-05-22 22:09 ` Philip Oakley
2013-05-22 22:15 ` Felipe Contreras
2013-09-13 21:23 ` [PATCH V2 0/3] Extend dot repository documentation Philip Oakley
2013-09-13 21:23 ` [PATCH V2 1/3] Doc URLs: relative paths imply the dot-respository Philip Oakley
2013-09-13 22:21 ` Junio C Hamano
2013-09-14 20:47 ` Philip Oakley
2013-09-13 21:23 ` [PATCH V2 2/3] config doc: update dot-repository notes Philip Oakley
2013-09-13 22:28 ` Junio C Hamano
2013-09-14 20:47 ` Philip Oakley
2013-09-13 21:23 ` [PATCH V2 3/3] doc: command line interface (cli) dot-repository dwimmery Philip Oakley
2013-09-13 22: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=1368964449-2724-3-git-send-email-philipoakley@iee.org \
--to=philipoakley@iee.org \
--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).