Re: Re: Re: Locking Working Copy File
From: Chris H Keith <ckeith_at_pacease.com>
Date: Thu, 27 Mar 2008 14:09:22 -0700 (PDT)
Other tools have the concept of "freezing" the version until released. I think this is what is desired here. You can accomplish the same with a branch of the unfinished versions. The new change sets in 1.5 will help.
Jean-Marc van Leerdam <j.m.van.leerdam_at_gmail.com> wrote: Jeffrey,
On 27/03/2008, Maze, Jeffrey S. <JMaze_at_co.geauga.oh.us> wrote: 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').
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.
-- Regards, Jean-Marc ---------------- ___ // \\ @@ "De Chelonian Mobile" / \_/ \/._) TortoiseSVN <\_/_\_/ / The coolest Interface to (Sub)Version Control /_/ \_\ Check out http://tortoisesvn.netReceived on 2008-03-27 22:09:34 CET
This is an archived mail posted to the TortoiseSVN Users mailing list.