From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Jakub Narebski <jnareb@gmail.com>
Subject: Re: [PATCH] Trim hint printed when gecos is empty.
Date: Tue, 28 Nov 2006 11:46:54 +0000 [thread overview]
Message-ID: <200611281146.56201.andyparkins@gmail.com> (raw)
In-Reply-To: <ekh5k8$vih$1@sea.gmane.org>
On Tuesday 2006 November 28 11:15, Jakub Narebski wrote:
> Yes. You are supposed to add Signed-off-by on commit (I hope that
> git-format-patch doesn't dulicate signoff lines), using git-commit -s.
> But perhaps a config option...
I achieve reasonable results by having the following in my .git/config
[format]
headers = "To: git@vger.kernel.org\n"
[alias]
email=format-patch --signoff --stdout
By tuning this per-project I know that a "git email" will generate the correct
sort of patch for this project.
The thing that's missing is a config option to make git-commit add the signoff
automatically. I think this would be useful, as "signing off" is probably a
per-project decision rather than a per-commit decision. It seems awkward to
require the user to remember what the project policy is and always get the
right git-commit for each project.
Andy
--
Dr Andy Parkins, M Eng (hons), MIEE
next prev parent reply other threads:[~2006-11-28 11:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 10:27 [PATCH] Trim hint printed when gecos is empty Han-Wen Nienhuys
2006-11-28 10:52 ` Han-Wen Nienhuys
2006-11-28 11:15 ` Jakub Narebski
2006-11-28 11:46 ` Andy Parkins [this message]
2006-11-28 13:28 ` Johannes Schindelin
2006-11-28 14:03 ` Andy Parkins
2006-11-28 14:40 ` Johannes Schindelin
2006-11-28 15:06 ` Andy Parkins
2006-11-28 15:31 ` Shawn Pearce
2006-11-28 18:29 ` Junio C Hamano
2006-11-29 9:29 ` Johannes Schindelin
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=200611281146.56201.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.