Brendan van Drempt wrote:
> Stefan,
>
> I an using Subversion/TortoiseSVN in the context of Website Development
> where the "different files at different revisions" occurs in the TEST or
> LIVE Websites NOT someone's personal development environment.
>
> If I wasn't to have different files at different revisions in these
> environments, how would I avoid showing committed changes that were not
> approved to go on the TEST/LIVE Websites, or Rollback to previous revisions
> for certain files etc.?
>
> If it is advised this isn't the best work practise, have you any information
> or advice on alternative work processes for this application? That would be
> greatly appreciated.
>
> Thanks.
>
> Brendan.
>
Hi,
So you are using a working copy for your live website? I guess that
working copy is from trunk. Why not create a branch called LIVE and
checkout a working copy from there and whenever a commit to trunk is
approved, merge it to LIVE?
Regards,
Peter Löfgren
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon May 9 07:40:25 2005