From: "James P. Howard, II" <jh@jameshoward.us>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add commit.infodisplay option to give message editor empty file
Date: Sat, 5 Dec 2009 18:09:03 -0500 [thread overview]
Message-ID: <20091205230903.GA3816@thermopylae.local> (raw)
In-Reply-To: <20091205162827.GA9584@sigill.intra.peff.net>
On Sat, Dec 05, 2009 at 11:28:27AM -0500, Jeff King wrote:
> If the latter, I think we would be better served by an option to simply
> turn off the template. Then that is also helpful for the case of people
> using decent editors, but who don't want to waste the CPU time on
> generating the template information (which can be substantial for things
> like media repositories).
Actually, I find this a reasonable solution for both cases and would be
willing to reimplment my change this way, as it meets my needs and would
be useful to others. The only question I have is, what should variable/
command line option be called?
James
--
James P. Howard, II, MPA MBCS
jh@jameshoward.us
next prev parent reply other threads:[~2009-12-05 23:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 23:04 [PATCH] Add commit.infodisplay option to give message editor empty file James P. Howard, II
2009-12-05 7:30 ` Junio C Hamano
2009-12-05 15:47 ` James P. Howard, II
2009-12-05 16:28 ` Jeff King
2009-12-05 23:09 ` James P. Howard, II [this message]
2009-12-06 4:22 ` Jeff King
2009-12-06 8:01 ` Junio C Hamano
2009-12-06 13:12 ` Jeff King
2009-12-07 22:45 ` [PATCH] Add commit.status, --status, and --no-status James P. Howard, II
2009-12-08 0:39 ` James Pickens
2009-12-08 6:04 ` Jeff King
2009-12-08 7:13 ` Junio C Hamano
2009-12-08 7:55 ` Jeff King
2009-12-08 14:07 ` James P. Howard, II
2009-12-07 22:43 ` [PATCH] Add commit.infodisplay option to give message editor empty file James P. Howard, II
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=20091205230903.GA3816@thermopylae.local \
--to=jh@jameshoward.us \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.