[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Feature Request - Copy Versioned Files

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: 2007-07-16 10:23:57 CEST

On 15/07/07, Dave Miller <dwmiller@umich.edu> wrote:
> I am developing an application that is sold in many custom configurations with
> 500 MB of non-versioned supporting files (images, a database, config files,
> etc.) When I fix a bug, I'd like to test it in several configurations. I can
> commit the fix and then update the other working copies of other configurations,
> but this commit is premature since I haven't really tested it fully yet.
> Would it be possible to have a feature that enabled one to move the source from
> one working copy to another? Like a copy/paste versioned files? I realize this
> runs counter to version control in general because I might be pasting over
> modified code. But I'd be willing to risk it!
> If this isn't a good idea, is there a good way to do this with existing
> features? Should I just create a tag like "Bug450_Temp" in the repository for
> holding an intermediate copy that I want to test?

How different are your configurations? Instead of having multiple WCs
and using update, can you have just one working copy and use Switch to
change between configurations?


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Jul 16 10:23:16 2007

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.