From: "Junio C Hamano" <gits...@pobox.com>
Sent: Friday, September 13, 2013 11:21 PM
Philip Oakley <philipoak...@iee.org> writes:
Signed-off-by: Philip Oakley <philipoak...@iee.org>
---
Documentation/urls.txt | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/urls.txt b/Documentation/urls.txt
index 9ccb246..5350a63 100644
--- a/Documentation/urls.txt
+++ b/Documentation/urls.txt
@@ -55,6 +55,13 @@ These two syntaxes are mostly equivalent, except
the former implies
--local option.
endif::git-clone[]
+Relative paths are relative to the `$GIT_DIR`, thus the path:
Is it?
git init src dst
I didn't think you could do that. It's not documented (initialise
multiple dirctories with the same command) and on msysgit if fails with
`usage:`. But I know what you mean.
cd src
git commit --allow-empty -m initial
cd ../dst
git fetch ../src HEAD:refs/heads/copy
would work, but if it is relative to $GIT_DIR, the last one would
need to be written as
git fetch ../../src HEAD:refs/heads/copy
wouldn't it?
Ah but... we are specifying a repository here, not a file path, so the
`$GIT_DIR` / '.git' discovery comes into it, I think. It's the
discovery of the relevant repository that I now realise I've not
included, which can be confusing in the various special cases. So the
relative paths comment will be incomplete [your point], and needs
something extra between "relative to" and "the $GIT_DIR".
+
+- '.'
+
+is the current repository and acts as if it were a repository
+named `'.'`.
+
When Git doesn't know how to handle a certain transport protocol, it
attempts to use the 'remote-<transport>' remote helper, if one
exists. To explicitly request a remote helper, the following syntax
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
