From: Philip Oakley <philipoakley@iee.org>
To: GitList <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>
Subject: [PATCH V3 1/2] doc: command line interface (cli) dot-repository dwimmery
Date: Sat, 21 Sep 2013 16:11:08 +0100 [thread overview]
Message-ID: <1379776269-4496-2-git-send-email-philipoakley@iee.org> (raw)
In-Reply-To: <1379776269-4496-1-git-send-email-philipoakley@iee.org>
The Git cli will accept dot '.' (period) as the relative path,
and thus the current repository. Explain this action.
Signed-off-by: Philip Oakley <philipoakley@iee.org>
---
This updates 431260cc8dd
Documentation/gitcli.txt | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/gitcli.txt b/Documentation/gitcli.txt
index b065c0e..50e4ce0 100644
--- a/Documentation/gitcli.txt
+++ b/Documentation/gitcli.txt
@@ -58,10 +58,10 @@ the paths in the index that match the pattern to be checked out to your
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 the filesystem '.' (period) refers to the current directory,
-using a '.' as a repository name in Git (a dot-repository) is a relative
-path for your current repository.
+
+ * Just as the filesystem '.' (period) refers to the current directory,
+ using a '.' as a repository name in Git (a dot-repository) is a relative
+ path and hence will be your current 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-09-21 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-21 15:11 [PATCH V3 0/2] Extend dot repository documentation Philip Oakley
2013-09-21 15:11 ` Philip Oakley [this message]
2013-10-15 21:57 ` [PATCH V3 1/2] doc: command line interface (cli) dot-repository dwimmery Junio C Hamano
2013-10-16 6:53 ` Philip Oakley
2013-09-21 15:11 ` [PATCH V3 2/2] Doc URLs: relative paths imply the dot-respository Philip Oakley
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=1379776269-4496-2-git-send-email-philipoakley@iee.org \
--to=philipoakley@iee.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
/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).