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

Re: [TSVN] Feature Request: Get Lock recursively by right-clicking a folder

From: SteveKing <stefankueng_at_gmail.com>
Date: 2005-06-06 12:58:29 CEST

On 6/6/05, Schmidt, Maik <Maik.Schmidt@mahr.de> wrote:

> > If the locking is mainly for communication, you could just pick one
> > important file, maybe the makefile, and lock that.
>
> Well, the project main sourcefile would be an option. But that wouldn't work for our lib - we are using a script language, there is no makefile, just script-files with subroutines.

So lock the files you're working on. I can't believe that your scripts
are written in a way that one change affects *all* script files. And
if it really does, you're better of rewriting those scripts (OO comes
to mind).

> > You can also set up a post-lock hook which sends everyone in
> > the team an
> > email when you get a lock. That way you (and your senior) get a record
> > of what everyone is working on. But you will have to look at
> > the sample
> > hook scripts to see how that is done. I have never done it myself.
>
> I've read the docs about hook scripts just briefly but don't you need a svn server for that? We are using TSVN working directly on the repository which is on a shared network drive. I think there is no intention to setup a full server.

No. The scripts are executed even if you access the repository via file:///.

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Jun 6 13:05:12 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.