From: "H. Peter Anvin" <hpa@zytor.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Andreas Ericsson <exon@op5.se>, git@vger.kernel.org
Subject: Re: [PATCH] git-commit: Having $GIT_COMMITTER_NAME implies -s
Date: Wed, 16 Nov 2005 21:27:54 -0800 [thread overview]
Message-ID: <437C14DA.8000905@zytor.com> (raw)
In-Reply-To: <7vbr0j3nku.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> I am not so sure about this. A Signed-off-by line used in the
> kernel and git projects has a specific meaning; you've read
> SubmittingPatches in either projects, have'nt you?
>
> I do work on a machine from which I make commits to both git
> project and my day-job work project. I do not necessarily want
> to add Signed-off-by line in commits I make for the latter.
>
More importantly, it's vital that a Signed-off-by: line is always added
with explicit awareness of the signer.
-hpa
prev parent reply other threads:[~2005-11-17 5:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 23:38 [PATCH] git-commit: Having $GIT_COMMITTER_NAME implies -s Andreas Ericsson
2005-11-17 4:28 ` Junio C Hamano
2005-11-17 5:27 ` H. Peter Anvin [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=437C14DA.8000905@zytor.com \
--to=hpa@zytor.com \
--cc=exon@op5.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).