From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Dmitry Ivankov <divanorama@gmail.com>
Cc: git@vger.kernel.org, Jonathan Nieder <jrnieder@gmail.com>,
David Barr <davidbarr@google.com>
Subject: Re: [PATCH 4/5] svn-fe: use svn-fe --no-progress in remote-svn-alpha
Date: Wed, 6 Jul 2011 15:26:40 +0530 [thread overview]
Message-ID: <CALkWK0mrpy2bho9ExHaCSenzZLoEKSo-T0K_FVDz9VtaQcY-2g@mail.gmail.com> (raw)
In-Reply-To: <1309884350-13415-5-git-send-email-divanorama@gmail.com>
Hi again,
Dmitry Ivankov writes:
> svn-fe by default produces a progress line for each imported revision.
> For large repos it stresses the terminal and a user, possibly scrolls
> away error messages.
>
> Just disable progress lines for now.
>
> Signed-off-by: Dmitry Ivankov <divanorama@gmail.com>
> ---
> contrib/svn-fe/git-remote-svn-alpha | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Perhaps squash this into the patch that introduces --[no]-progress in svn-fe?
-- Ram
next prev parent reply other threads:[~2011-07-06 9:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 16:45 [PATCH 0/5] remote-svn-alpha updates Dmitry Ivankov
2011-07-05 16:45 ` [PATCH 1/5] svn-fe: use svnrdump --quiet in remote-svn-alpha Dmitry Ivankov
2011-07-05 16:45 ` [PATCH 2/5] svn-fe: allow svnadmin instead of svnrdump in svn helper Dmitry Ivankov
2011-07-06 10:12 ` Ramkumar Ramachandra
2011-07-06 11:02 ` Dmitry Ivankov
2011-07-06 11:11 ` Ramkumar Ramachandra
2011-07-06 11:28 ` Jonathan Nieder
2011-07-05 16:45 ` [PATCH 3/5] svn-fe: add a test for remote-svn-alpha Dmitry Ivankov
2011-07-05 16:45 ` [PATCH 4/5] svn-fe: use svn-fe --no-progress in remote-svn-alpha Dmitry Ivankov
2011-07-06 9:56 ` Ramkumar Ramachandra [this message]
2011-07-06 12:30 ` Jonathan Nieder
2011-07-05 16:45 ` [PATCH 5/5] svn-fe: use proper refspec " Dmitry Ivankov
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=CALkWK0mrpy2bho9ExHaCSenzZLoEKSo-T0K_FVDz9VtaQcY-2g@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=davidbarr@google.com \
--cc=divanorama@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.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).