From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "James P. Howard\, II" <jh@jameshoward.us>, git@vger.kernel.org
Subject: Re: [PATCH] Add commit.infodisplay option to give message editor empty file
Date: Sun, 06 Dec 2009 00:01:53 -0800 [thread overview]
Message-ID: <7v7ht0jzta.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20091206042206.GC23983@coredump.intra.peff.net> (Jeff King's message of "Sat\, 5 Dec 2009 23\:22\:06 -0500")
Jeff King <peff@peff.net> writes:
> I would be tempted to call it "--no-template", but I think that is too
> confusing. The "--template" option is not really about the git-generated
> template, but about a user-defined template that goes on top of the
> git-generated one (I would have expected --template=/dev/null to do what
> you want, too, but it retains the git template).
>
> Probably "--no-status" would be a good name, as the generated template
> is the format generated by "git status".
I wonder which part is the most expensive in generating the status
output. Perhaps -suno is sufficient?
next prev parent reply other threads:[~2009-12-06 8:02 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
2009-12-06 4:22 ` Jeff King
2009-12-06 8:01 ` Junio C Hamano [this message]
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=7v7ht0jzta.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jh@jameshoward.us \
--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.