git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-commit-tree(1): correct description of defaults
Date: Thu, 10 Jan 2013 10:33:59 -0800	[thread overview]
Message-ID: <7vr4ls28h4.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1357820998.10754.6.camel@vanquo.pezone.net> (Peter Eisentraut's message of "Thu, 10 Jan 2013 07:29:58 -0500")

Peter Eisentraut <peter@eisentraut.org> writes:

> The old phrasing indicated that the EMAIL environment variable takes
> precedence over the user.email configuration setting, but it is the
> other way around.
>
> Signed-off-by: Peter Eisentraut <peter@eisentraut.org>
> ---

It could be argued that the observed behaviour is a bug, by the way.

If we followed the normal "command line options trump environment
variables that in turn trump config variables that in turn trump
whatever the default values we compute using cues from the system"
precedence order, EMAIL ought to come between the more specific
GIT_{AUTHOR,COMMITTER}_EMAIL environment variables and the
user.email configuration variable.

But reading the value of EMAIL can also be seen as part of the
"using cues from the system" (it often is set in equivalents of
"$HOME/.profile" by equivalents of "adduser") step, and the original
motivation to add user.email indeed was to allow users to override
EMAIL (or the name we grab from the system) without having to set
the GIT_COMMITTER_EMAIL environment variable.

So the current behaviour is correct, and the patch is a good
(belated ;-) update to the documentation.

Will apply.  Thanks.

>  Documentation/git-commit-tree.txt |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/git-commit-tree.txt b/Documentation/git-commit-tree.txt
> index 6d5a04c..a221169 100644
> --- a/Documentation/git-commit-tree.txt
> +++ b/Documentation/git-commit-tree.txt
> @@ -72,13 +72,13 @@ if set:
>  	GIT_COMMITTER_NAME
>  	GIT_COMMITTER_EMAIL
>  	GIT_COMMITTER_DATE
> -	EMAIL
>  
>  (nb "<", ">" and "\n"s are stripped)
>  
>  In case (some of) these environment variables are not set, the information
>  is taken from the configuration items user.name and user.email, or, if not
> -present, system user name and the hostname used for outgoing mail (taken
> +present, the environment variable EMAIL, or, if that is not set,
> +system user name and the hostname used for outgoing mail (taken
>  from `/etc/mailname` and falling back to the fully qualified hostname when
>  that file does not exist).

      reply	other threads:[~2013-01-10 18:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 12:29 [PATCH] git-commit-tree(1): correct description of defaults Peter Eisentraut
2013-01-10 18:33 ` Junio C Hamano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vr4ls28h4.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=peter@eisentraut.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).