git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v1] Documentation: git-rev-parse: clarify that --git-dir does not necessarily show relative paths

From
Jonathan Nieder <jrnieder@gmail.com>
Date
May 18, 2012, 09:31 UTC
Message-ID
<20120518093159.GA31412@burratino>
In-Reply-To
<1337333004-23164-1-git-send-email-jon.seymour@gmail.com>
Jon Seymour wrote:
Show 12 quoted lines
> --- a/Documentation/git-rev-parse.txt
> +++ b/Documentation/git-rev-parse.txt
> @@ -137,7 +137,8 @@ shown.  If the pattern does not contain a globbing character (`?`,
>  
>  --git-dir::
>  	Show `$GIT_DIR` if defined. Otherwise show the path to
> -	the .git directory, relative to the current directory.
> +	the .git directory. The path shown, when relative, is
> +	relative to the current working directory.
>  +
>  If `$GIT_DIR` is not defined and the current directory
>  is not detected to lie in a git repository or work tree
Thanks for taking care of it.

I suppose I'd have used a subject line like the following for brevity.

	rev-parse doc: --git-dir does not always show a relative path
For what it's worth, with or without that change,
Acked-by: Jonathan Nieder <jrnieder@gmail.com>
Previous: Jon SeymourNext: Junio C Hamano
Message 5 of 7 in “git rev-parse --git-dir does report yield relative path to git directory, per documentation”
  1. Jon SeymourMay 17, 2012
  2. Junio C HamanoMay 17, 2012
  3. Jonathan NiederMay 17, 2012
  4. Documentation: git-rev-parse: clarify that --git-dir does not necessarily show relative pathsJon Seymour, May 18, 2012
  5. Jonathan NiederMay 18, 2012
  6. Junio C HamanoMay 18, 2012
  7. Nguyen Thai Ngoc DuyMay 18, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.