From: Alex Riesen <raa.lkml@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Use diff* with --exit-code in git-am, git-rebase and git-merge-ours
Date: Sun, 25 Mar 2007 11:33:45 +0200 [thread overview]
Message-ID: <20070325093345.GA2563@steel.home> (raw)
In-Reply-To: <7vwt15c150.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano, Sun, Mar 25, 2007 08:01:31 +0200:
> However, I have a few comments.
>
> Have you run any benchmark? I suspect "and speeds things up" is
I didn't benchmark any of these, so I can't backup the statement with
the number but...
> a gross overstatement. A qualified "SOMETIMES speeds things up"
> would be a more honest thing to say.
it must speed things up, if only for removed shell-side efforts to
redirect the output and store it in heap. To overstatement it I should
have said: "greatly speeds things up".
next prev parent reply other threads:[~2007-03-25 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-25 0:56 [PATCH] Use diff* with --exit-code in git-am, git-rebase and git-merge-ours Alex Riesen
2007-03-25 6:01 ` Junio C Hamano
2007-03-25 9:33 ` Alex Riesen [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-25 0:42 Alex Riesen
2007-03-25 0:49 ` Alex Riesen
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=20070325093345.GA2563@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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 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).