From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Steven Grimm <koreth@midwinter.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Teach git-commit about commit message templates.
Date: Mon, 23 Jul 2007 11:40:33 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707231136530.14781@racer.site> (raw)
In-Reply-To: <46A481B4.7000502@midwinter.com>
Hi,
On Mon, 23 Jul 2007, Steven Grimm wrote:
> Johannes Schindelin wrote:
> > Up until here, I was with you. But this feels very wrong.
> >
> > Why not compare COMMIT_MSG to the templatefile, if there is one? I.e.
> >
> > test ! -z "$templatefile" && cmp "$GIT_DIR"/COMMIT_MSG "$templatefile" &&
> > die "Unchanged message; will not commit"
> >
>
> The template can itself have comments -- instructions or explanations of
> fields to fill in, for example -- and since comments have been stripped
> from COMMIT_MSG at this point, a comparison against such a template
> would always fail.
Ah, I missed that. But IIRC your patch does not wrap that logic behind
test ! -z "$templatefile", right? So this is my modified suggestion:
test ! -z "$templatefile" && {
grep -vie '^Signed-off-by:' < "$GIT_DIR"/COMMIT_MSG" > "$GIT_DIR"/tmp1
grep -ve '^#' < "$templatefile" > "$GIT_DIR"/tmp1
trap 'rm "$GIT_DIR"/tmp[12]' 0
cmp "$GIT_DIR"/tmp[12] &&
die "Unchanged message; will not commit"
}
Ciao,
Dscho
next prev parent reply other threads:[~2007-07-23 10:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 4:17 [PATCH] Teach git-commit about commit message templates Steven Grimm
2007-07-23 10:04 ` Johannes Schindelin
2007-07-23 10:23 ` Steven Grimm
2007-07-23 10:40 ` Johannes Schindelin [this message]
2007-07-23 10:56 ` Steven Grimm
2007-07-23 11:58 ` Johannes Schindelin
2007-07-23 17:12 ` Junio C Hamano
2007-07-24 12:01 ` Steven Grimm
2007-07-24 21:43 ` Junio C Hamano
2007-07-25 6:42 ` Steven Grimm
2007-07-25 7:39 ` Junio C Hamano
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=Pine.LNX.4.64.0707231136530.14781@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=koreth@midwinter.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).