From: Martin Waitz <tali@admingilde.org>
To: Junio C Hamano <junkio@cox.net>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: [PATCH] Kill the useless progress meter in merge-recursive
Date: Fri, 20 Apr 2007 11:00:10 +0200 [thread overview]
Message-ID: <20070420090010.GD27208@admingilde.org> (raw)
In-Reply-To: <7vd51z317c.fsf@assigned-by-dhcp.cox.net>
[-- Attachment #1: Type: text/plain, Size: 283 bytes --]
hoi :)
On Fri, Apr 20, 2007 at 01:21:59AM -0700, Junio C Hamano wrote:
> I would propose removing the progress meter for "Checking out
> files" in unpack-trees, for the same reason.
well, for large trees it is indeed useful, so I'd like to leave it in.
--
Martin Waitz
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-04-20 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 6:37 [PATCH] Kill the useless progress meter in merge-recursive Shawn O. Pearce
2007-04-20 8:21 ` Junio C Hamano
2007-04-20 9:00 ` Martin Waitz [this message]
2007-04-20 15:14 ` Linus Torvalds
2007-04-20 18:00 ` Daniel Barkalow
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=20070420090010.GD27208@admingilde.org \
--to=tali@admingilde.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--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).