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

Re: Need to adjust based on svn:execute

From: Bryan Donlan <bdonlan_at_hikari.afraid.org>
Date: 2005-02-10 19:55:29 CET

Hash: SHA1

Buddy Burden wrote:
| Guys,
| Okay, here's the situation: My user's working copy is on a Linux box,
| where it has to be (it's a web site and the Apache server runs on
| Linux). The directory is Samba mounted out to the user's Windows
| machine so that she can use TortoiseSVN to do all her Subversion
| activities, 'cause she's not a command line kinda gal (and, no, this
| isn't a TortoiseSVN question; read on).
| Now, what happens when she does the TortoiseSVN equivalent of an svn
| update is that she gets a bunch of CGI scripts with no execute bits
| set. Which of course isn't TortoiseSVN's fault; it has no idea that it
| needs to set them, and couldn't do it through Samba anyway (at least
| AFAIK). But it's still a problem.
| Now, the first thing my user does whenever something doesn't work well
| is run her bounce_apache script (one of the few things she does from the
| Linux command line). It occurs to me that if I could just add a line
| (or several) into that script to tell Subversion to update all the
| execute bits, I'd be set. Unfortunately, running svn update does
| nothing, because AFA Subversion is concerned, the files _are_ updated.
| Is there a way I can ask Subversion to check all the files' svn:execute
| property and adjust the execute bit accordingly? TIA.

Delete and revert them. Or possibly have her run that script whenever
she updates the site, and have it run 'svn up' on a different wc on the
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 10 19:58:17 2005

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

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