Guten Tag Z W,
am Sonntag, 20. Januar 2013 um 00:56 schrieben Sie:
> 2-
> We thought svnlook is only available for the remote svn server but it
> seems we can execute it.
> We thought svnlook is a svn server command and not a svn client
> command - are we correct ?
Look at the help or manpage for
Z W wrote:
>Hi All
>
>We're new to subversion.
>
>We like to make sure we get the latest svn revision number from the
>svn repository on the remote server.
>We are confused as to which command to use to find our latest revision
>number.
>Questions
>1-
>Which is correct -
>svn info url or
>svnlo
On Sat, Jan 19, 2013 at 7:42 AM, Karl Heinz Marbaise wrote:
>
> so after thinking about the concept...
> it does not make sense to go further with a shared working copies on a
> network drive there are too many issues (of course, cause SVN is not made
> for such things)..so i will drop the idea...
Hi All
We're new to subversion.
We like to make sure we get the latest svn revision number from the
svn repository on the remote server.
We are confused as to which command to use to find our latest revision number.
Questions
1-
Which is correct -
svn info url or
svnlook youngest
2-
We thought s
> From: Raghu GS
>To: users@subversion.apache.org
>Sent: Tuesday, January 15, 2013 8:46 AM
>Subject: Authentication failure when SVNParentPath used
>I regret for bugging you once again.
>Apache authentication for the particular repository is failing when i use
>SVNParentPath, but working well w
Hi,
Thanks for a very interesting issue to look at.
I'm happy to report that I would now call this issue fixed:
I think we can call this a known issue as it has been known for quite some
time.
A workaround for this issue would be to do an explicit update of the missing
I'm not 100% sure how to reproduce this yet, but updating the folder to r0
and then updating it again should give you all children again. (You can also
use -set-depth excluded, and then an explicit update on the target)
I don't have suggestions on how you can do this with TortoiseSVN.
Karl Heinz Marbaise wrote on Sat, Jan 19, 2013 at 14:42:30 +0100:
> Hi,
>
>> Have you considered other solutions? For example, the ASF CMS maintains
>> one working copy per project, and uses zfs copy-on-write clones to fork
>> off a per-user working copy for each user (even concurrent users) who
>
Hi,
> You'll need to think about permissions: when wc.db is rewritten, or
a new .svn/pristine/ file created, would user2 have permissions to
replace or unlink it (respectively)?
Authz would be a concern too, if the two users' read accesses differ.
(the code should DTRT --- it's no different tha
