Re: git-svn: Missing files

From: Eric Wong <normalperson@yhbt.net>
Date: Jul 20, 2006, 02:48 UTC
Message-ID: <20060720024815.GC31763@localdomain>
In-Reply-To: <b6327a230607191909tf48c4f8nc551b732523cca3e@mail.gmail.com>

Ben Williamson <benw@pobox.com> wrote:

> Oh. I just looked in git-svn and found this:
> 
> $VERSION = '1.1.1-broken';

I removed the version tag and started using GIT_VERSION when git-svn moved out of contrib/ a few weeks ago.

As far as I remember, I don't remember git-svn having problems with missing files. There has been a bug where it got extra files from other places in the repository, but that's fixed.

May I ask if you have the Perl SVN:: library bindings installed? If so 1.1.1-broken (and all versions afterwards) will automatically. use them (if the SVN library version is >= 1.1).

Nevertheless, I'm running an import right now (with the SVN:: libraries enabled) and will make another run with them disabled (which is kind of slow). I'll keep you posted...

I've actually been getting a lot of real-world git-svn usage in the past few weeks (and hence the lack of git-related work) and haven't noticed any major problems.

> Fair enough. So far I haven't explored other branches in git.git, I've
> no idea what "pu" stands for. Can someone point me in the right
> direction?

pu is "potential updates", it's very bleeding edge. next is a few steps ahead of master, which should be the safest of the three.

-- 
Eric Wong