git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Eric Wong" <normalperson@yhbt.net>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: git-svn strangeness with tags and Squirrelmail repo
Date: Wed, 20 Jun 2007 21:13:18 +1200	[thread overview]
Message-ID: <46a038f90706200213p2d1e3ba3nf58107584afe4901@mail.gmail.com> (raw)
In-Reply-To: <20070620072446.GC25010@muzzle>

On 6/20/07, Eric Wong <normalperson@yhbt.net> wrote:
> Martin Langhoff <martin.langhoff@gmail.com> wrote:
> > First -- kudos to Eric Wong and company: git-svn can deal with the odd
> > errors and invalid chunks of XML or UTF-8 that SVN spits at me every
> > once in a while. And it "just works" in 99% of the situation. Great
> > stuff.
>
> You're welcome.  At the same time I'm not reallu sure what you mean by
> "odd errors and invalid chunks of XML or UTF-8 that SVN spits at me"
> unless it's some joke about SVN I'm not getting :)

Oh - the Squirrelmail SVN repo is one of those that have commits that
SVN itself cannot read due to invalid data. So git-svnimport, by
virtue of using the Perl SVN bindings, fails to import it.

git-svn, by some other virtue, imports it perfectly ;-)

> >   [svn-remote "svn"]
> >        url = http://squirrelmail.svn.sourceforge.net/svnroot/squirrelmail
> >        fetch = trunk/squirrelmail:refs/heads/svn/trunk
> >        branches = branches/*/squirrelmail:refs/heads/svn/*
> >        tags = tags/*/squirrelmail:refs/tags/svn/*
>
> git-svn expects 'refs/remotes/' in the local ref name.  Otherwise,
> the left-hand side is correct.

Good to know!

> > and when I do that -- trunk and branches do what I want, but tags
> > aren't imported anymore. :-/
>
> Now its odd to me that trunks and branches even works with those ref
> names.

I'm lucky then ;-)

My reason for the "alternative" locations is to match a bit better the
v1.5.0 behaviour re branches, tags and remotes, and to run the import
directly into a bare repo on git.catalyst.net.nz

 - Tags, by virtue of landing under refs/remotes are being treated as
heads rather than tags. That's why I want to have them in
refs/tags/<bla>/*

 - If branches + trunk end up in refs/remotes then my bare repo /
gateway doesn't work well - -refs/remotes aren't cloned or fetched

 - gitweb refuses to show those heads/tags (maybe it's because it's an
old version?)

cheers,


martin

  reply	other threads:[~2007-06-20  9:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-20  5:05 git-svn strangeness with tags and Squirrelmail repo Martin Langhoff
2007-06-20  7:24 ` Eric Wong
2007-06-20  9:13   ` Martin Langhoff [this message]
2007-06-20 10:33     ` Peter Baumann

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=46a038f90706200213p2d1e3ba3nf58107584afe4901@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=normalperson@yhbt.net \
    /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).