From: Nicolas Pitre <nico@cam.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] common progress display support
Date: Wed, 18 Apr 2007 15:20:28 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0704181517360.4504@xanadu.home> (raw)
In-Reply-To: <20070418185649.GB18328@spearce.org>
On Wed, 18 Apr 2007, Shawn O. Pearce wrote:
> Nicolas Pitre <nico@cam.org> wrote:
> > Note: I left merge-recursive.c out since it has a strange notion of
> > progress as it apparently increase the expected total number as it goes.
> > Someone with more intimate knowledge of what that is supposed to mean
> > might look at converting it to the common progress interface.
>
> That disaster in merge-recursive.c is my fault. The progress
> meter there doesn't mean much of anything.
>
> I've been thinking about getting rid of it.
Well... be my guest. ;-)
Nicolas
next prev parent reply other threads:[~2007-04-18 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 18:27 [PATCH] common progress display support Nicolas Pitre
2007-04-18 18:56 ` Shawn O. Pearce
2007-04-18 19:20 ` Nicolas Pitre [this message]
2007-04-19 9:03 ` Johannes Schindelin
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=alpine.LFD.0.98.0704181517360.4504@xanadu.home \
--to=nico@cam.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).