From: Eric Wong <normalperson@yhbt.net>
To: Seth Falcon <sethfalcon@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git svn fetch spewing warnings
Date: Tue, 27 Mar 2007 12:00:04 -0700 [thread overview]
Message-ID: <20070327190004.GD16591@localdomain> (raw)
In-Reply-To: <m28xdkvsxx.fsf@ziti.fhcrc.org>
Seth Falcon <sethfalcon@gmail.com> wrote:
> Hi,
>
> I'm using git 1.5.1.rc1.13.g0872 and I just tried the following to
> create a new git-svn tracked repository.
>
> I did:
>
>
> git svn init $URL
> git svn fetch
> # I also tried git svn fetch --no-follow-parent
>
> The command eventually completed and left me with a working
> repository, but in the process I had screenfuls of warning messages
> like this:
We now try harder to find previous versions of the path we're tracking.
I've also changed the window from 1000 to 100 revisions, so the
warning message spewing is 10 times more frequent. Don't worry, though
it's harmless :)
--
Eric Wong
next prev parent reply other threads:[~2007-03-27 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 17:02 git svn fetch spewing warnings Seth Falcon
2007-03-27 19:00 ` Eric Wong [this message]
2007-03-27 19:17 ` Seth Falcon
2007-03-31 0:54 ` [PATCH] git-svn: avoid respewing similar error messages for missing paths Eric Wong
2007-04-02 10:30 ` Seth Falcon
2007-04-02 18:46 ` 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=20070327190004.GD16591@localdomain \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=sethfalcon@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).