Skip to contentSkip to conversation

Documentation/git: add missing info about --git-dir command-line option

PATCH Superseded Manlio Perillo 2 participants 4 messages Jun 15, 2016 Documentation

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore

Manlio Perillo

author
#0 lore raw

PATCH 1/1 Documentation/git: add missing info about --git-dir command-line option

The Documentation/git.txt file, in the GIT_DIR environment variable section, did not mentioned that this value can also be set using the --git-dir command line option.

---
 Documentation/git.txt | 1 +
 1 file changed, 1 insertion(+)
Documentation/git.txt +1 -0
index e643683..60db292 100644
@@ -650,6 +650,7 @@ git so take care if using Cogito etc.
 	If the 'GIT_DIR' environment variable is set then it
 	specifies a path to use instead of the default `.git`
 	for the base of the repository.
+	The '--git-dir' command-line option also sets this value.
  'GIT_WORK_TREE'::
 	Set the path to the working tree.  The value will not be
Signature · 1 line
1.8.0.1.347.gf94c325.dirty
#1 lore raw
Quoted 4 lines · Manlio Perillo

The Documentation/git.txt file, in the GIT_DIR environment variable section, did not mentioned that this value can also be set using the --git-dir command line option.
---

s/mentioned/mention/; Also it may help to say

Unlike other environment variables (e.g. GIT_WORK_TREE, GIT_NAMESPACE),

somewhere in the description.

Please sign-off your patch (see Documentation/SubmittingPatches).

Thanks.

Quoted 14 lines
 Documentation/git.txt | 1 +
 1 file changed, 1 insertion(+)
Documentation/git.txt +1 -0
index e643683..60db292 100644
@@ -650,6 +650,7 @@ git so take care if using Cogito etc.
 	If the 'GIT_DIR' environment variable is set then it
 	specifies a path to use instead of the default `.git`
 	for the base of the repository.
+	The '--git-dir' command-line option also sets this value.
  'GIT_WORK_TREE'::
 	Set the path to the working tree.  The value will not be
author
#2 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Il 12/12/2012 20:35, Junio C Hamano ha scritto:

Quoted 9 lines
Quoted 4 lines · Manlio Perillo

The Documentation/git.txt file, in the GIT_DIR environment variable section, did not mentioned that this value can also be set using the --git-dir command line option.
---

s/mentioned/mention/; Also it may help to say

Quoted 9 lines

Unlike other environment variables (e.g. GIT_WORK_TREE, GIT_NAMESPACE),

somewhere in the description.

Please sign-off your patch (see Documentation/SubmittingPatches).

Thanks.

Thanks to you.

I have sent the updated patch, let me know if is ok.

Manlio Perillo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlDKF9YACgkQscQJ24LbaUQyHwCcDiaJjFZ5vwHzxjHyhEBCyFdd GnIAn34MjoWmQOcLKJEl/EpE0ImeQBLG
=yrux
-----END PGP SIGNATURE-----

author
#3 lore raw
In reply to Junio C Hamano

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Il 12/12/2012 20:35, Junio C Hamano ha scritto:

Quoted 7 lines
Quoted 4 lines · Manlio Perillo

The Documentation/git.txt file, in the GIT_DIR environment variable section, did not mentioned that this value can also be set using the --git-dir command line option.
---

Quoted 5 lines

s/mentioned/mention/; Also it may help to say

Unlike other environment variables (e.g. GIT_WORK_TREE, GIT_NAMESPACE),

I'm sorry, I just copied this text "as is" (I'm lazy) in the commit message failing to notice the use of the tab character.

When I checked the patch email message, my editor rendered the tab character as a single space...

That's the reason why I have all my editors configured to never ever use tabs.

Manlio Perillo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlDLYUMACgkQscQJ24LbaUTUPACcDhufXkawZZPBV0p/af1GFu1D /BcAnjPARpeTi4EdyM/3wV0eI9U9Fu51
=rSfl
-----END PGP SIGNATURE-----