From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Cc: Seth Falcon <sethfalcon@gmail.com>
Subject: Re: format-patch signoff argument no longer works
Date: Wed, 31 May 2006 12:02:33 -0700 [thread overview]
Message-ID: <7vejyayq46.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: m2mzcycn4f.fsf@ziti.fhcrc.org
Seth Falcon <sethfalcon@gmail.com> writes:
> Matthias Kestenholz <lists@spinlock.ch> writes:
>
>> * Geoff Russell (geoffrey.russell@gmail.com) wrote:
>>> It appears to have got lost when the shell script got converted to C.
>>>
>> Yes, this was intentional. You should sign off your changes while
>> committing (git commit -s|--signoff)
A bit on this later, but first to clear one thing up...
> When should one commit _without_ signoff?
>
> The obvious answer is: when one doesn't approve of the changes in the
> commit... But in my usual workflow, commit means
> works-for-me-I-think-it-is-good. :-)
Please, calm down and read Documentation/SubmittingPatches,
item (6), to understand what sign-off means. It does not have
anything to do with the result of the commit "working". I do
not use -s when making commits during my day-job, for example.
We do not want to make sign-off the default. It has to be a
concious act on the signer's part to add one. Otherwise it
would not carry much weight.
About the droppage of "format-patch -s", I have come to think of
it as a mistake (yes, I can change my mind). Consider:
* You are the leader of a group of people who hack on a part of
the kernel, internally in your company. You and other
developers make improvements and make commits, with "git
commit -s".
* As the in-company integrator, you maintain the canonical
"company tree" by pulling from others in your group.
* It's time to send good pieces to Linus and/or Andrew and as
the group lead you are responsible for sending them out. The
commits would have Sign-off's by the original committers, but
as the contact person (representative) of your group, your
name is better recognizable in the outside community, and as
the leader of your group, it is a good practice for _you_ to
vouch for what your group did.
In that scenario, in addition to what "commit -s" gives us, it
is handy for the person who is sending the patches out via
e-mail to add his own sign-off.
Now, we could do that by re-adding "format-patch -s" option, or
alternatively we could add that to "send-email". We might want
to do both ;-)
next prev parent reply other threads:[~2006-05-31 19:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <93c3eada0605310332p19241861g466e1516a2aaf0df@mail.gmail.com>
2006-05-31 11:11 ` format-patch signoff argument no longer works Geoff Russell
2006-05-31 11:28 ` Matthias Kestenholz
2006-05-31 13:58 ` Seth Falcon
2006-05-31 14:09 ` Johannes Schindelin
2006-05-31 19:02 ` Junio C Hamano [this message]
2006-05-31 19:19 ` J. Bruce Fields
2006-05-31 19:43 ` Seth Falcon
2006-05-31 22:14 ` [PATCH] format-patch --signoff Junio C Hamano
2006-05-31 22:42 ` Johannes Schindelin
2006-05-31 23:16 ` Junio C Hamano
2006-05-31 23:31 ` Johannes Schindelin
2006-05-31 14:14 ` [PATCH] Update documentation for git-format-patch Dennis Stosberg
2006-05-31 15:00 ` Johannes Schindelin
2006-05-31 15:24 ` Jakub Narebski
2006-05-31 17:24 ` Dennis Stosberg
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=7vejyayq46.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=sethfalcon@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 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).