From: Junio C Hamano <gitster@pobox.com>
To: Abhijit Bhopatkar <bain@devslashzero.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation: Better explain git-commit --author implications
Date: Fri, 17 Oct 2008 21:55:05 -0700 [thread overview]
Message-ID: <7vfxmuec46.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <48F95974.3010503@devslashzero.com> (Abhijit Bhopatkar's message of "Sat, 18 Oct 2008 09:05:16 +0530")
Abhijit Bhopatkar <bain@devslashzero.com> writes:
> '--author' changes the author name and email, but the
> documentation was not clear that it will not affect the
> '--signoff' option which will still use the user's name and
> email from the git settings.
>
> Signed-off-by: Abhijit Bhopatkar <bain@devslashzero.com>
> ---
> Documentation/git-commit.txt | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt
> index eb05b0f..17b69fa 100644
> --- a/Documentation/git-commit.txt
> +++ b/Documentation/git-commit.txt
> @@ -78,7 +78,8 @@ OPTIONS
> Override the author name used in the commit. You can use the
> standard `A U Thor <author@example.com>` format. Otherwise,
> an existing commit that matches the given string and its author
> - name is used.
> + name is used. This has no effect on singoff line which will
> + still use commiter name and email .
>
> -m <msg>::
> --message=<msg>::
> @@ -95,6 +96,7 @@ OPTIONS
> -s::
> --signoff::
> Add Signed-off-by line at the end of the commit message.
> + '--author' option has no effect on this line.
I think it is much clearer if you do not say what does _not_ affect
things, but instead say what does. So let's do this instead.
--signoff::
Add Signed-off-by line by the committer at the end of the commit
log message.
And no other changes.
By making it clear that signoff is about the committer, it would be clear
that --author (or GIT_AUTHOR_NAME environment variable) would not affect
it.
next prev parent reply other threads:[~2008-10-18 4:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 3:35 [PATCH] Documentation: Better explain git-commit --author implications Abhijit Bhopatkar
2008-10-18 4:55 ` Junio C Hamano [this message]
2008-10-19 4:19 ` [PATCH] Documentation: Clarify '--signoff' for git-commit Abhijit Bhopatkar
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=7vfxmuec46.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).