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: Sat, 11 Feb 2006 00:16:11 +1300 [thread overview]
Message-ID: <1139570171.12123.29.camel@localhost.localdomain> (raw)
In-Reply-To: <200602092301.21098.linuxfood@linuxfood.net>
On Thu, 2006-02-09 at 23:01 -0800, Brian Smith wrote:
> > > While that is an admirable goal, unless you can point me to something
> > > that will allow you to actually commit back to SVN without a working
> > > copy,
> > Such as SVK
> > http://svk.elixus.org/
> > (svn url: http://svn.openfoundry.org/svk/)
> Well, after reading through a number of pages I discovered something:
> "The repository created is actually a Subversion repository. In other words,
> you could use any subversion commands with that repository." [*1*]
> So, while it is a technicality, there is an SVN Repo, which is what
> I'm trying to avoid[...
Yes, currently there is - but let me show you what's under the hood
briefly... as you notice later;
> (Incidentally, the allure of the SVN perl bindings had me for awhile, but
> after trying to decipher the horrid PODs for it decided that Bash was just
> easier. )
Yes, there are SWIG bindings for various languages. In debian/ubuntu the
Perl bindings will be built to the package libsvn-core-perl.
Take a look at this module:
http://search.cpan.org/dist/SVN-Simple/lib/SVN/Simple/Edit.pm
That uses the above module and allows you to construct a Subversion
commit and try to apply it.
The documentation's a bit weak, but AFAIK the basic functionality is
there and a lot better an abstraction than the raw bindings themselves.
SVN::Mirror:
http://search.cpan.org/dist/SVN-Mirror/lib/SVN/Mirror.pm
can go the other way.
> (the point being to have a git repo after all, for
> the purpose of using git commands), perhaps it would be worth looking
> into to see if I could somehow utilize the svk svn repo (since there
> are space savings) for the SVN working copy. [*2*]
That's right - in principle, SVK could be plumbed to have a git
repository in its ~/.svk/local - then you could have one git repo, and a
head for each mirrored project.
But don't concern yourself with my plans - it seems our tastes in
porcelain differ ;)
Sam.
prev parent reply other threads:[~2006-02-10 11:16 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
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 [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=1139570171.12123.29.camel@localhost.localdomain \
--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 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).