All of the sudden, starting somewhere prior to 1.7.13, the $PATH variable
is set, although the svnbook states
"For security reasons, the Subversion repository executes hook programs
with an empty environment—that is, no environment variables are set at all,
not even $PATH (or %PATH%, under Windows)
Hi,
I have a question regarding the right behavior of info and status commands on
file externals and new files resisting in 'X'-folders. This is what I do:
jruhe@wheezy:~$ svn co
svn://wheezy.wks.berl.axway.int/ms_automatic/mapping_services/projects/scratch%20pad/DML_EMPTY
ADML_EMPTY/Docum
issue. Thank you for your reply
Greetings,
Julian
-Ursprüngliche Nachricht-
Von: Stefan Sperling [mailto:s...@elego.de]
Gesendet: Dienstag, 18. Dezember 2012 18:27
An: Julian Ruhe
Cc: users@subversion.apache.org
Betreff: Re: Semantics of locking a "revision"
On Tue, Dec 18, 201
Hello,
if I co a working copy with -rREV with REV older than HEAD, I am able to get a
lock on any file. But it seems to me, that the lock is never published to the
server as no "svn info URL" shows an existing lock on the file on any working
revision, while the lock is existing in my wc (displa
