From: Junio C Hamano <gitster@pobox.com>
To: Mike Hommey <mh@glandium.org>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] Use user.name and user.email in import-tars.perl
Date: Sun, 24 Feb 2008 10:06:38 -0800 [thread overview]
Message-ID: <7v3arixm8h.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1203857838-29505-1-git-send-email-mh@glandium.org> (Mike Hommey's message of "Sun, 24 Feb 2008 13:57:18 +0100")
Mike Hommey <mh@glandium.org> writes:
> Mimic what is done in git-import.sh and git-import.perl
>
> Signed-off-by: Mike Hommey <mh@glandium.org>
> ---
>
> And that made me wonder if it wouldn't be worth, actually, to have
> git config user.name and git config user.email return the "magic" values
> gotten from guessing in ident.c when no value is in the config. That would
> allow scripts, which have no other simple means to get the user name and
> email, to have the same feature as builtins.
Or perhaps use "git var GIT_COMMITTER_IDENT"?
next prev parent reply other threads:[~2008-02-24 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 12:57 [PATCH] Use user.name and user.email in import-tars.perl Mike Hommey
2008-02-24 18:06 ` Junio C Hamano [this message]
2008-09-07 8:52 ` [PATCH] Use GIT_COMMITTER_IDENT instead of hardcoded values " Mike Hommey
2008-09-07 17:09 ` Junio C Hamano
2008-09-08 14:51 ` Johannes Schindelin
2008-09-08 20:40 ` Junio C Hamano
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=7v3arixm8h.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mh@glandium.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).