Well, the reasoning is that we have three files in a previous revision.
These haven't been fully tested, ok'd and the web programmers are still
working out the kinks. They've been submitted into the SVN and are
being tracked by our service desk software (so they can't be removed
from the repository; e.g. 'My web page doesn't work' - 'fixed in svn rev
952').
But there are other changes to the website which are being submitted,
approved and being updated for the live site.
If I could lock these three files at the previous revision (prior to the
debugging changes), I wouldn't have to keep make the changes manually
when it could possibly be automatically done via great programs like SVN
and TSVN. That's all.
Thanks..
________________________________
From: Jean-Marc van Leerdam [mailto:j.m.van.leerdam_at_gmail.com]
Sent: Thursday, March 27, 2008 4:21 PM
To: users_at_tortoisesvn.tigris.org
Subject: Re: Re: Locking Working Copy File
Hi Jeffrey,
On 27/03/2008, Maze, Jeffrey S. <JMaze_at_co.geauga.oh.us> wrote:
Actually, that's not quite what I was looking for.
Say there is a file, default.html. It and my working copy are
at
revision 950 and I'm using this to test something. There's an
update of
other files as well as this default.html file; but since I'm
testing
using the older version of the file, how do I lock my working
copy of
default.html (rev 950) so if other revisions are submitted, the
other
files are updated, but default.html is locked at revision 950;
even if
there's updates to it.
Why would you want to update your working copy while testing in rev.950
(you would have a mixed state during the tests)?
Or you do the 'update to rev. 950' on the file again after you update
the working copy to HEAD.
--
Regards,
Jean-Marc
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-03-27 21:38:19 CET