Re: [ jEdit-devel ] SourceForge CVS

[Slava P. <sp...@gj...>]

mike dillon wrote:
> i don't think that jEdit should leave the GJT. i propose that since SourceForge
> allows the use of cron jobs, we set up a cron job on shell1.sourceforge.net to
> sync the CVS on SourceForge with the main repository on the GJT, do all the
> necessary updates and committing changes. i'm not sure yet if it can be done
> securely though, so don't get your hopes up.
> 
> failing actually setting it up on SourceForge, i could set up the cron job
> securely on jedit.standmed.com and do the requisite leg work there.
> 
> i'm not sure what level of granularity could be provided, but hopefully CVS
> would let us mirror all changes from the GJT tree to the SourceForge tree, so
> that the SourceForge commit record would be just a record of the batching done
> to keep it up-to-date.

This is going to be more trouble than it's worth. You will need to keep
track of additions, removals, locks, and so on. If all this can be dealt
with easily, I suggest we do it backwards from how you propose; have
the 'primary' tree at SF, and just commit the org.gjt.sp.jedit package
to the GJT every once in a while. But why bother with having two trees
at all?

Slava