> From: Ben Collins-Sussman <sussman@collab.net>
> Subject: Re: Subversion suggestion...
>
> David Bovill <david.bovill@opn-technologies.com> writes:
>
>> I was thinking of pushing/mirroring data to the CVS repository. Developers
>> could then say:
>>
>> "OK, everyone wants / expects CVS access, but I can justify going down
>> the Subversion root at this stage because I can mirror to CVS and provide
>> anonymous CVS access on Sourceforge."
>
> Sure, this is easy to do with any SCM system, as long as the system
> has 'post-commit' hooks. Subversion's own repository has a
> post-commit hook script that mails out a unified diff of the commit's
> changes to all svn developers. You could tweak that script to apply
> the very same diff to a CVS working copy and run 'cvs commit'. It's a
> no-brainer.
>
>> Commits that go through Subversion would be "pushed" to the CVS on
>> Sourceforge.
>>
>>> Anyway, I'm only one of 10+ svn developers. If you want real feedback,
>>> post your question to dev@subversion.tigris.org. :-)
>>>
>>
>> Lets see how to subscribe... thanks
>
> We'd love to have you join us!
>
OK - howdy :)
OK - on issue here applies only to us unfortunate souls that do not have
direct access to a public server, and therefore need to work with a low cost
ISP. Unfortunately my ISP has removed CVS recently from the server set up...
so this is going to be hard.
It is a lot easier to install Apache modules with an ISP than CVS - so
anyone have any suggestions as to how to get Subversion to update a CVS
Sourceforge repository automatically?
An ideal would be a built in commit_to_cvs module - no fancy stuff, that
would all be done in Subversion. Another option is to have a public service
/ web service for this...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:07 2006