From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/3] show: turn on rename progress
Date: Thu, 24 Mar 2011 13:45:56 -0400 [thread overview]
Message-ID: <20110324174556.GA30661@sigill.intra.peff.net> (raw)
In-Reply-To: <7v39mca7hl.fsf@alter.siamese.dyndns.org>
On Thu, Mar 24, 2011 at 08:00:38AM -0700, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > On Wed, Mar 23, 2011 at 02:25:02PM -0700, Junio C Hamano wrote:
> >
> > We could also turn it on for "git log" in that case, though it is only
> > useful if the first commit happens to be the one that is slow.
> >
> > I should also turn it on for "git diff". I'll prepare a cleaner series
> > with that in it, too.
>
> Sounds good, thanks.
Here it is:
[1/4]: pager: save the original stderr when redirecting to pager
[2/4]: progress: use pager's original_stderr if available
[3/4]: show: turn on rename detection progress reporting
[4/4]: diff: turn on rename detection progress reporting
> > What about the degrade-cc-to-c warnings? Are you working on another
> > revision, or should I re-roll your changes on top of my series, handling
> > the "one-warning-per-commit" behavior I suggested when stdout and stderr
> > are combined?
>
> Also sounds good, thanks. No, I am spending far more time on ushering
> stalled topics than looking at my weatherbaloons and no time left for the
> latter.
I thought this would be simple on top of 1/4 above, but it's not. In
some cases we want to insert the warning before the diff output, and in
some cases we want to know afterwards what happened. Which means we
probably need to carry a new "show the warning" flag in diffopt and
respect it in the rename, but also fill out the needed_rename_limit.
-Peff
next prev parent reply other threads:[~2011-03-24 17:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 21:45 [PATCH] builtin/diff.c: remove duplicated call to diff_result_code() Junio C Hamano
2011-03-22 21:50 ` [PATCH 1/3] diffcore-rename: refactor "too many candidates" logic Junio C Hamano
2011-03-22 21:50 ` [PATCH 2/3] diffcore-rename: record filepair for rename src Junio C Hamano
2011-03-22 21:50 ` [PATCH 3/3] diffcore-rename: fall back to -C when -C -C busts the rename limit Junio C Hamano
2011-03-23 15:58 ` Jeff King
2011-03-23 16:41 ` Junio C Hamano
2011-03-23 16:50 ` Jeff King
2011-03-23 18:17 ` Jeff King
2011-03-23 18:18 ` [PATCH 1/3] pager: save the original stderr when redirecting to pager Jeff King
2011-03-23 18:19 ` [PATCH 2/3] progress: use pager's original_stderr if available Jeff King
2011-03-23 18:19 ` [PATCH 3/3] show: turn on rename progress Jeff King
2011-03-23 21:25 ` Junio C Hamano
2011-03-24 14:50 ` Jeff King
2011-03-24 15:00 ` Junio C Hamano
2011-03-24 17:45 ` Jeff King [this message]
2011-03-24 17:46 ` [PATCH 1/4] pager: save the original stderr when redirecting to pager Jeff King
2011-03-24 17:47 ` [PATCH 2/4] progress: use pager's original_stderr if available Jeff King
2011-03-24 17:49 ` [PATCH 3/4] show: turn on rename detection progress reporting Jeff King
2011-03-24 23:35 ` Junio C Hamano
2011-03-24 17:51 ` [PATCH 4/4] diff: " Jeff King
2011-03-25 8:35 ` Johannes Sixt
2011-03-25 9:09 ` Jeff King
2011-03-24 23:03 ` [PATCH 3/3] show: turn on rename progress Junio C Hamano
2011-03-25 6:17 ` Jeff King
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=20110324174556.GA30661@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).