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

Re: Re: Need to check a file out, but want never to check it back in !

From: Simon Large <simon.tortoisesvn_at_gmail.com>
Date: Thu, 4 Nov 2010 22:22:44 +0000

On 4 November 2010 17:58, Richard M Willis <RichardW_at_pulsar-pm.com> wrote:
>> On 4 November 2010 17:34, Dave Huang <khym at
>
>> The other down side to this is that the file is always marked as
>> modified. Like ignoring compiler warnings instead of fixing them, one
>> day you are going to miss a real warning because you are so used to
>> ignoring the 'usual' warnings. For me, if there is red on my WC then
>> it means something needs attention.
>
> For me, also. I want to make sure there is no red anywhere.
>
> I am sort of going to go with the "use a template" approach, which is (to me) the obviousest way of doing it.
>
> I can't believe there's no automatic-copy available though; every other build tool that I use has a "run this batch file when finished" option. How come there's no equiv in TSVN ?

TortoiseSVN is not a build tool, it's a revision control tool ;-) and
it does have client side hooks to do exactly that.

> If it is a security issue, then at least let *me* the user/manager of the system decide whether it'll be a valid thing to do.

That would make checkout an unsafe operation. If you go to a public
repository and checkout what you think is some useful source code, you
would not want the owner of the repository to be able to booby trap it
and execute code of their choosing on your PC. That decision has to
remain at the client end, which unfortunately means that what you want
to achieve cannot be done safely.

> Having to get people to remember to "copy blah.template to blah" is obviously not a show-stopper, but shouldn't be necessary in this day-and-age. The workflow here basically involves cleaning your working directory when you've finished committing stuff (don't like leaving stuff hanging around).

Agreed, but it is the compiler which is broken, not the version
control tool. In a traditional make environment, the build process can
be set to create missing directories and copy files from templates
before the build starts. Your system won't even start if that file is
missing. Not a lot we can do about that.

Simon

-- 
:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2678943
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-11-04 23:23:01 CET

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