From: Junio C Hamano <gitster@pobox.com>
To: Steven Drake <sdrake@xnet.co.nz>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add `commit.signoff` configuration variable.
Date: Wed, 13 Jan 2010 00:30:21 -0800 [thread overview]
Message-ID: <7v1vhuquea.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1001131635510.16395@vqena.qenxr.bet.am> (Steven Drake's message of "Wed\, 13 Jan 2010 16\:36\:44 +1300 \(NZDT\)")
You need to defend this one better, in fact a *lot* better, than other
ones. See
http://thread.gmane.org/gmane.comp.version-control.git/32503/focus=32522
http://thread.gmane.org/gmane.comp.version-control.git/103939/focus=104207
for starters. Your justifications should address all the points raised in
previous threads.
prev parent reply other threads:[~2010-01-13 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 3:36 [PATCH] Add `commit.signoff` configuration variable Steven Drake
2010-01-13 4:36 ` Steven Drake
2010-01-13 8:30 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v1vhuquea.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sdrake@xnet.co.nz \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).