Git development
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: Brian Gernhardt <benji@silverinsanity.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-svn + svn:externals
Date: Thu, 22 Feb 2007 13:48:54 -0800	[thread overview]
Message-ID: <20070222214854.GA32195@localdomain> (raw)
In-Reply-To: <51167308-9E52-4E46-80A0-70A3C255C081@silverinsanity.com>

Brian Gernhardt <benji@silverinsanity.com> wrote:
> Is there any plan or shell incantation to get git-svn working nicely  
> with SVN externals?  I'm working a Ruby on Rails application  
> (radiantcms.org), which uses the externals to track library  
> versions.  I don't mind reading from an SVN repository, but would  
> much much rather use git to track my local changes.
> 
> Also, is it possible for git-svn to at least warn when the repo  
> you're importing has externals?  It would be nicer than randomly  
> having hunks of the project missing.

The latest versions of git-svn should warn about externals (among some
other things that we currently don't support).  They are logged in
.git/svn/$refname/unhandled.log with newlines (and some other
characters) URI-encoded out.  I've been planning on having something
parse the unhandled.log but have not gotten around to it.

I'm still waiting on subproject support in git to seriously look at
svn:externals; but it's not a high priority for me.  You could probably
look at the code that does 'git svn show-ignore' which reads the
svn:ignore properties and expand it to support svn:externals.

-- 
Eric Wong

      reply	other threads:[~2007-02-22 21:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-22 16:10 git-svn + svn:externals Brian Gernhardt
2007-02-22 21:48 ` Eric Wong [this message]

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=20070222214854.GA32195@localdomain \
    --to=normalperson@yhbt.net \
    --cc=benji@silverinsanity.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