From: Sam Vilain <sam@vilain.net>
To: Brian Smith <linuxfood@linuxfood.net>
Cc: git@vger.kernel.org
Subject: Re: Tracking and committing back to Subversion?
Date: Tue, 07 Feb 2006 12:23:43 +1300 [thread overview]
Message-ID: <43E7DA7F.6060503@vilain.net> (raw)
In-Reply-To: <200602040727.30965.linuxfood@linuxfood.net>
Brian Smith wrote:
>>Has anyone done any work on bidirectional access to SVN repositories?
>>ie, tracking and committing.
> I'm working on something that does just that, I haven't gotten to the
> bidirectional part just yet. (The only reason I didn't use git-svnimport is
> that it has a /terrible/ time importing from the KDE svn repo. )
Indeed, mirroring SVN repositories via SVN::Mirror (which is used by
SVK) can take hours for large projects with thousands of commits.
> My take on the properties, though I like your thoughts on how to handle at
> least svn:ignore, is to basically just let svn deal with them. I will make a
> couple tools that will modify them, for interface reasons, but they'll just
> be wrappers around the svn commands themselves.
> At the moment, the tools are written as bash shell scripts with an
> interface I'm trying to keep as intuitive as cogito (even though I use
> the core-git tools now.)
Right; I was looking for an approach that did not require working copies
of the remote subversion repository to be kept locally. Still, perhaps
that approach has merit, though I would probably start in Perl and use
SVK::Simple (see CPAN) to give a richer SVN mirroring API.
Are you planning on publishing these scripts?
Sam.
next prev parent reply other threads:[~2006-02-06 23:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 22:51 Tracking and committing back to Subversion? Sam Vilain
2006-02-04 5:40 ` Eric Wong
2006-02-04 19:51 ` Seth Falcon
2006-02-06 23:12 ` Sam Vilain
2006-02-04 15:27 ` Brian Smith
2006-02-06 23:23 ` Sam Vilain [this message]
2006-02-10 0:50 ` Brian Smith
2006-02-10 0:54 ` Junio C Hamano
2006-02-10 1:06 ` Brian Smith
2006-02-10 4:27 ` Sam Vilain
2006-02-10 7:01 ` Brian Smith
2006-02-10 11:16 ` Sam Vilain
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=43E7DA7F.6060503@vilain.net \
--to=sam@vilain.net \
--cc=git@vger.kernel.org \
--cc=linuxfood@linuxfood.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.