> Your process sounds odd to me -- is it really individual
> *files* that get promoted from one branch to another? Or is
> it *changesets* that get promoted? The latter is the more
> common case.
>
> For example, someone fixes a bug in the devel branch. The
> change is then 'ported' (via 'svn merge') to the qa branch
> for testing. If it's all good, the change is then applied to
> the production branch.
>
> So if that's what you're talking about, this is just a matter
> of doing merges from branch to branch. Very common stuff.
>
> If you're really talking individual file promotion, then
> yeah, sure, I guess you can manually copy them around. As
> Francois said, you can just run 'svn copy URL1 URL2.' No
> need for working copies. But this case seems odd to me.
> Version control is usually about managing sets of changes,
> not about juggling individual files.
Hi Ben,
Thanks for the comments. I left a bit of the history of our in-house
source control system out. It is currently one folder with a heap of
files in it, not organised by project or anything like that (which
obviously has some deficiencies). Sounds like a nightmare I know, and
hopefully it will change in the future. So for the moment moving single
files around seems the logical way to go for these legacy files.
Cheers,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 22 05:35:26 2003