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

Re: Problems with "svn status" command and NTFS junction points

From: Juanma Barranquero <jmbarranquero_at_wke.es>
Date: 2004-03-02 11:16:31 CET

On Tue, 02 Mar 2004 10:55:20 +0100 (CET)
Branko Cibej <brane@xbc.nu> wrote:

> Another insteresting data point is that "svnadmin hotcopy" will igonore symlinks
> in the hooks directory, which is unfortunate if you link your hook scripts in
> from sonewhere else

Hmm... Curious. I my repositories, the whole hooks/ dir is a junction. I
usually do:

 C:\data\repos> svnadmin create new-one
 C:\data\repos> cd new-one
 C:\data\repos\new-one> rd /s hooks
 C:\data\repos\new-one> junction hooks C:\data\hooks

(C:\data\hooks is my main hooks/ dir)

After that:

 C:\data\repos> svnadmin hotcopy new-one c:\data\backup\new-one

copies the whole repository, hooks and all.

> (as I do, so that I can keep the hooks in an SVN WC, guess
> why :-).

I've found less error prone to have the hooks in a SVN wc elsewhere, but
copy them to C:\data\hooks when they're ready. The problem with my
junction approach is that, every now and then, I do:

 C:\data\repos> rd /s test-repo

and I accidentally remove C:\data\hooks contents too. To stop that, now I
have an empty read-only file in C:\data\repos named
thanks to 4NT colored directory listings :)


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 2 11:15:41 2004

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