From: Paolo Bonzini <bonzini@gnu.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git-commit: add a prepare-commit-msg hook
Date: Mon, 21 Jan 2008 13:59:27 +0100 [thread overview]
Message-ID: <4794972F.9000007@gnu.org> (raw)
In-Reply-To: <alpine.LSU.1.00.0801211231480.5731@racer.site>
>> Sure it won't break anything, but it won't work either! The existing
>> message hook runs after the editing session -- I want the hook to
>> introduce text that is merely a suggestion that the user can delete, or
>> a template that the user needs to customize further.
>
> OMG you're right. But why didn't you say so in the commit message?
> Something like "This hook complements the commit-msg hook, in that it runs
> _before_ the editor is launched".
I can't believe this. ;-) At least I'm laughing for something nice now!
You're right, I should have said instead of this:
> The prepare-commit-msg hook is run whenever a "fresh" commit message
> (i.e. not one taken from another commit with -c) is shown in the editor.
... just before a "fresh" commit message is shown in the editor.
^^^^^^
>>> Also, the change would be non-intrusive, easy-to-review
>> Please. That's ludicrous.
>>
>> My patch is 3 lines of inserted code and 0 modified lines, checking one
>> variable that is set once in builtin-commit.c (edit_message).
>
> Actually, after reading the commit message I was in
> "this-is-not-necessary" mode, and therefore the diffstat looked too large
> for me.
Yes, but still the diffstat was all .txt files... ;-)
> Actually, reading your patch again I think it also triggers for "-c", as
> well as for "[-C|-F|-m] ... -e".
Not for "-c", that's the point of the "edit_message" check. You're
right about "-e" though.
Points taken, and patch will be resubmitted after 1.5.4.
Paolo
next prev parent reply other threads:[~2008-01-21 13:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 14:51 [PATCH] git-commit: add a prepare-commit-msg hook Paolo Bonzini
2008-01-18 15:47 ` Johannes Schindelin
2008-01-18 15:51 ` Paolo Bonzini
2008-01-18 16:06 ` Johannes Schindelin
2008-01-18 16:37 ` Paolo Bonzini
2008-01-18 18:06 ` Johannes Schindelin
2008-01-18 18:51 ` Paolo Bonzini
2008-01-18 19:01 ` Benoit Sigoure
2008-01-18 19:05 ` Alex Riesen
2008-01-18 19:46 ` Paolo Bonzini
2008-01-18 21:08 ` Alex Riesen
2008-01-18 22:05 ` Junio C Hamano
2008-01-19 9:32 ` Paolo Bonzini
2008-01-19 11:20 ` Johannes Schindelin
2008-01-19 15:41 ` Benoit Sigoure
2008-01-19 16:04 ` Paolo Bonzini
2008-01-20 22:28 ` Junio C Hamano
2008-01-21 6:16 ` Paolo Bonzini
2008-01-21 11:04 ` Johannes Schindelin
2008-01-21 12:14 ` Paolo Bonzini
2008-01-21 12:46 ` Johannes Schindelin
2008-01-21 12:59 ` Paolo Bonzini [this message]
2008-01-21 22:44 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2008-01-21 14:27 Paolo Bonzini
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=4794972F.9000007@gnu.org \
--to=bonzini@gnu.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).