From: Junio C Hamano <gitster@pobox.com>
To: bain <bain@devslashzero.com>
Cc: git@vger.kernel.org
Subject: Re: git-commit does not signoff using name supplied by --author
Date: Fri, 17 Oct 2008 16:58:07 -0700 [thread overview]
Message-ID: <7vhc7ag4fk.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 0f761673-f0ec-4689-b1f1-8019d4540b0c@i20g2000prf.googlegroups.com
bain <bain@devslashzero.com> writes:
>> If i use git-commit --author "A U Thor <author.example.net>" -s it
>> still uses my global author.name and author.email to add signoff
>> message.
>>
>> Is this expected behavior?
>
> Never mind...
>
> Looking at the code i found out commiter name/email is used to
> signoff, which is correct and can be different than author.
Actually we _do mind_. The users should not have to look at the code to
find this out.
Send in a patch to clarify this in the documentation if it is not already
done, please.
prev parent reply other threads:[~2008-10-17 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 10:11 git-commit does not signoff using name supplied by --author bain
2008-10-17 10:31 ` bain
2008-10-17 23:58 ` 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=7vhc7ag4fk.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=bain@devslashzero.com \
--cc=git@vger.kernel.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).