On 9/1/2011 7:49 AM, Vladimir Avdonin wrote: > Regarding you experimental work: > > The mechanism for such activity provided by subversion is branch. Once you > created you branch you can screw it around in any way you please, it would > not affect main line of development and releases. Once your branch would > arrive to some agreeable good state, it can be merged back into trunk for > common use.
The only problem with that is that, back when I started it, Sourceforge wasn't using SVN, it was using CVS. SVN understands files getting *moved* to other folders, while CVS treats them as though you deleted the old file and created a new one in the new location. So, the revision history gets "broken", in a way. I'm now worried that, if I try to make a branch, SVN won't understand any continuity from the existing source tree, and it will consider the entire source code to be new.... which would make for an interesting merge into the trunk, later. But I know almost nothing about how SVN does it's thing... - Joe ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________ Jsynthlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
