From: Deskin Miller <deskinm@umich.edu>
To: git@vger.kernel.org
Cc: gitster@pobox.com
Subject: Re: [PATCH] git-svn: Print revision while searching for earliest use of path
Date: Thu, 5 Feb 2009 08:42:42 -0500 [thread overview]
Message-ID: <86d4c5e00902050542n74b10bfdw5e9249ac23fdc9e7@mail.gmail.com> (raw)
In-Reply-To: <86d4c5e00902050540lf8a3adfq18b1fed909d6e68a@mail.gmail.com>
Resending due to temporary insanity with email, sorry Eric.
On Thu, Feb 5, 2009 at 01:42, Eric Wong <normalperson@yhbt.net> wrote:
> Deskin Miller <deskinm@umich.edu> wrote:
>> If the current version is
>> felt to be too verbose since it is printing a new line, I'd be up for
>> squelching the output to e.g. every 1000 revisions or so.
>
> This is definitely useful on slow/large repositories. The current
> output with newlines is fine by me.
Ok.
> Couldn't we avoid the trouble of parsing the inconsistent error
> messages by printing this status message after the get_log() calls
> in gs_fetch_loop_common() ?
I didn't look at get_log closely, because I thought it executed only
once. I definitely agree that it would be cleaner if it's possible.
Let me look at the code some more and I'll see what I can do, or feel
free to post an alternate implementation.
Deskin Miller
next prev parent reply other threads:[~2009-02-05 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 5:09 [PATCH] git-svn: Print revision while searching for earliest use of path Deskin Miller
2009-02-05 6:42 ` Eric Wong
[not found] ` <86d4c5e00902050540lf8a3adfq18b1fed909d6e68a@mail.gmail.com>
2009-02-05 13:42 ` Deskin Miller [this message]
2009-02-09 0:33 ` [PATCH v2] " Deskin Miller
2009-02-09 21:22 ` Eric Wong
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=86d4c5e00902050542n74b10bfdw5e9249ac23fdc9e7@mail.gmail.com \
--to=deskinm@umich.edu \
--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).