From: Junio C Hamano <junkio@cox.net>
To: Shawn Pearce <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Automatically line wrap long commit messages.
Date: Wed, 31 May 2006 23:37:13 -0700 [thread overview]
Message-ID: <7v3beptm92.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060601033430.GA13485@spearce.org> (Shawn Pearce's message of "Wed, 31 May 2006 23:34:30 -0400")
Shawn Pearce <spearce@spearce.org> writes:
> Because git-commit currently performs a status update and throws
> that data into the editor buffer. That takes longer than committing
> from the command line. Especially if I've just done a git-diff or
> git-status to see what is changed and about to be committed...
Ah, why does it take this many exchanges to extract the true
motive behind what people do even in a technical forum like
this, I wonder...
So what you want is not multiple -m options nor piping to fmt.
What you really want is an option that is the opposite of -v to
git-commit that omits the status list ("_could_ commit if you
update-index" part -- since "will commit" is something we would
need to compute anyway).
> On a project the size of GIT on a Unix system this isn't a big deal;
> on a 9000 file project on Cygwin this difference is significant
> to me.
I suspect you are suffering from lstat() performance. I wonder
if "assume unchanged" git help your situation?
prev parent reply other threads:[~2006-06-01 6:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 8:57 [PATCH] Automatically line wrap long commit messages Shawn Pearce
2006-05-29 9:00 ` Jan-Benedict Glaw
2006-05-29 9:14 ` Shawn Pearce
2006-05-29 9:16 ` Junio C Hamano
2006-05-29 9:46 ` Shawn Pearce
2006-05-30 8:38 ` Junio C Hamano
2006-05-31 2:18 ` Shawn Pearce
2006-05-31 5:05 ` Junio C Hamano
2006-06-01 3:34 ` Shawn Pearce
2006-06-01 6:37 ` Junio C Hamano [this message]
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=7v3beptm92.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/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).