Hi,
In Subversion 1.6 'svn lock ' in a read-only workspace fails as expected
and no lock is created either in the workspace or in the repository.
In Svn 1.7/1.8 'svn lock ' still fails, but it creates a repository-side
lock (see below). Is this a regression or was the change intentional?
> svn
On 05/28/2012 09:06 PM, Philip Martin wrote:
Fergus Slorach writes:
If a directory containing svn:needs-lock files is copied and
committed, the needs-lock files are left writeable.
I think that is correct behaviour.
The problem is that a needs-lock file should not be writeable without
ergus
On 05/27/2012 10:53 AM, Bert Huijben wrote:
-Original Message-
From: Fergus Slorach [mailto:sug...@gmail.com]
Sent: zaterdag 26 mei 2012 23:57
To: dev@subversion.apache.org
Subject: File permissions are incorrect after directory copy in 1.7
In Subversion 1.7.5:
If a dire
In Subversion 1.7.5:
If a directory containing svn:needs-lock files is copied and
committed, the needs-lock files are left writeable.
The writeable state can be resolved by running 'svn revert' on
the files, even though the status indicates there is nothing to
revert.
Recipe and run-through res
s/downloads/wc/A/D/H' is not under version control
and is not part of the commit, yet its child
'/home/fergus/downloads/wc/A/D/H/psi' is part of the commit
On 11/13/2011 11:30 PM, Daniel Shahaf wrote:
On Sunday, November 13, 2011 11:07 PM, "Fergus Slorach"
wrote:
Hi
Hi Daniel,
Thanks for the quick response.
Here's the recipe - this works in 1.6 but fails with 1.7
All the best,
fergus
On 11/13/2011 07:03 PM, Daniel Shahaf wrote:
On Sunday, November 13, 2011 1:31 PM, "Fergus Slorach" wrote:
For 'undelete' in svn, we do th
For 'undelete' in svn, we do the following:
> svn rm bic4
> svn commit -m 'Test delete'
Deleting bic4/schematic
Committed revision 6
> svn merge --change -6 .
--- Reverse-merging r6 into '.':
Abic4
Abic4/schematic
Abic4/schematic/thumbnail_128x128.png
Abic4/schematic/mas
7 matches
Mail list logo
