"Philip Oakley" <[email protected]> wrote:
Shouldn't this `(identical to "git diff --relative")` also be
included in the documentation change? It would truly clarify the
intenbt for the reader.
Updated as follows:
+diff.relative::
+ Show pathnames relative to the current directory and exclude
+ changes outside this directory; equivalent to the 'git diff'
+ option '--relative'.
"Junio C Hamano" <[email protected]> wrote:
There should be a way to run non-relative diff in a repository that
has the configuration set, perhaps by overriding with some command
line option (e.g. "--no-relative").
Good idea; I'll put together a second patch for a "--no-relative" option
to disable diff.relative.
-----Original Message-----
From: Junio C Hamano <[email protected]>
Sent: 12/20/2014 09:58 PM
To: Philip Oakley <[email protected]>
CC: <[email protected]>, "Git Mailing List" <[email protected]>,
"Duy Nguyen" <[email protected]>, "Jonathan Nieder" <[email protected]>
Subject: Re: [PATCH v2] git-config support for diff.relative setting
"Philip Oakley" <[email protected]> writes:
From: <[email protected]>
By default, git-diff shows changes and pathnames relative to the
repository root. Setting the diff.relative config option to "true"
shows pathnames relative to the current directory and excludes
changes outside this directory (identical to "git diff --relative").
Shouldn't this `(identical to "git diff --relative")` also be included
in the documentation change? It would truly clarify the intenbt for
the reader.
A configuration that sticks a non-default behaviour without a way to
revert to the default is a no-no.
There should be a way to run non-relative diff in a repository that
has the configuration set, perhaps by overriding with some command
line option (e.g. "--no-relative").
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
