From: Eric Wong <normalperson@yhbt.net>
To: Ben Williamson <benw@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: git-svn: Missing files
Date: Wed, 19 Jul 2006 19:48:15 -0700 [thread overview]
Message-ID: <20060720024815.GC31763@localdomain> (raw)
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
next prev parent reply other threads:[~2006-07-20 2:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 2:02 git-svn: Missing files Ben Williamson
2006-07-20 2:09 ` Ben Williamson
2006-07-20 2:48 ` Eric Wong [this message]
2006-07-20 3:06 ` Eric Wong
2006-07-20 4:31 ` Ben Williamson
2006-07-20 3:48 ` [PATCH] " Eric Wong
2006-07-20 5:51 ` Ben Williamson
2006-07-20 8:43 ` [PATCH] git-svn: fix fetching new directories copies when using SVN:: libs Eric Wong
2006-07-24 6:42 ` Junio C Hamano
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=20060720024815.GC31763@localdomain \
--to=normalperson@yhbt.net \
--cc=benw@pobox.com \
--cc=git@vger.kernel.org \
/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).