Chris Cannam wrote:
On Friday 24 Feb 2006 10:48, Guillaume Laurent wrote:
I was thinking the same. The 'rosegarden' module was defined only as a
band-aid over our initial cvs import goofs, which we can now fix through
svn moves.
You want to handle that one?
With pleasure :-). (die cvs ! DIE !)
- commit reports to the bugs list, with diffs (I rely heavily on these
in tracking for branch management and will certainly continue to do so)
It would be surprising that sforge hadn't provided the same kind of
scripts they have for cvs for svn, I'll investigate.
They have, I've enabled it. Don't know whether it works or not yet though.
I'll make a dummy commit on one of the utility scripts and see what
happens. Is it supposed to post on rg-bugs like previously ?
Described here : https://sourceforge.net/docs/E09/#backup. I just
checked that it works (261Mb folks...).
Ugh, five times the size of the CVS tarball -- I guess that's an uncompressed
Subversion tree?
Yes, I just ran du -sh on it. What do we care, these days you get 250Gig
for 100 euros anyway.
I'll have a go too. rsync makes more sense in the long
run, I guess.
It's certainly better than re-downloading the whole cvs tarball each day.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
