From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: Christian Couder <christian.couder@gmail.com>,
Jacob Keller <jacob.keller@gmail.com>, git <git@vger.kernel.org>,
Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [PATCH v2 2/2] trailer: support multiline title
Date: Wed, 26 Aug 2015 18:15:11 +0200 [thread overview]
Message-ID: <vpqpp2akovk.fsf@anie.imag.fr> (raw)
In-Reply-To: <xmqqk2siujak.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Wed, 26 Aug 2015 09:05:39 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> While the reordering would certainly stop showing the comments and
> patch, I am not sure if that is a move in the right direction. It
> will rob from the hooks information that they have traditionally
> been given---
The information given in the comments do not have a 100% stable format,
and the hook is executed after letting the user possibly edit or delete
it, so I'm tempted to say that a hook using the commit comment is
broken.
Using the diff in the hook _is_ really broken: it relies on the user
calling "git commit" with -v, and there's nothing to garantee that.
> it will break some hooks.
It will also repair some hooks that were broken, but whose breakage was
never noticed or never explained.
> After all, interpret-trailers was invented exactly because we did not
> want individual hooks to roll their own ways to detect the end of the
> message proper, so the command should know where the message ends.
Right, but you can't prevent people from writting
command-that-shows-stuff >> "$1"
in their commit-msg hook. And these people will keep wondering why their
hook "sometimes doesn't work" (that's how I considered it for a while,
it took me a few commits to notice the correlation between "-v" and lack
of sign-off).
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2015-08-26 16:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 2:51 [PATCH v2 1/2] trailer: ignore first line of message Christian Couder
2015-08-26 2:51 ` [PATCH v2 2/2] trailer: support multiline title Christian Couder
2015-08-26 6:07 ` Matthieu Moy
2015-08-26 6:28 ` Jacob Keller
2015-08-26 14:53 ` Christian Couder
2015-08-26 16:05 ` Junio C Hamano
2015-08-26 16:15 ` Matthieu Moy [this message]
2015-08-26 19:48 ` Junio C Hamano
2015-08-29 4:00 ` Christian Couder
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=vpqpp2akovk.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=chriscool@tuxfamily.org \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacob.keller@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).