threads / patch / 32323

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

Subject: [PATCH] Documentation/git: add missing info about --git-dir command-line option

## tl;dr

4 messages between Dec 12, 2012 and Dec 14, 2012. Diffs are folded; open one to read it.

replies: 3people: 2as markdown or json

Manlio Perillo· Dec 12, 2012, 17:04 UTC · lore
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(+)
Show changes to Documentation/git.txt +1 −0
diff --git a/Documentation/git.txt b/Documentation/git.txt
index e643683..60db292 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -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
-- 
1.8.0.1.347.gf94c325.dirty
Junio C Hamano· Dec 12, 2012, 19:35 UTC · re: Manlio Perillo · lore

Re: [PATCH] Documentation/git: add missing info about --git-dir command-line option

Manlio Perillo <manlio.perillo@gmail.com> writes:
> 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.
Show 14 quoted lines
>  Documentation/git.txt | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/git.txt b/Documentation/git.txt
> index e643683..60db292 100644
> --- a/Documentation/git.txt
> +++ b/Documentation/git.txt
> @@ -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
Manlio Perillo· Dec 13, 2012, 18:00 UTC · re: Junio C Hamano · lore

Re: [PATCH] Documentation/git: add missing info about --git-dir command-line option

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Il 12/12/2012 20:35, Junio C Hamano ha scritto:
Show 18 quoted lines
> Manlio Perillo <manlio.perillo@gmail.com> writes:
> 
>> 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.
> 
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-----

Manlio Perillo· Dec 14, 2012, 17:26 UTC · re: Junio C Hamano · lore

Re: [PATCH] Documentation/git: add missing info about --git-dir command-line option

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Il 12/12/2012 20:35, Junio C Hamano ha scritto:
Show 12 quoted lines
> Manlio Perillo <manlio.perillo@gmail.com> writes:
> 
>> 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),
> 

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-----

← back to recent threads