Hi,
I'm using in my project externals set to explicit revision.
When using svn1.7+ the command "svn status -v -u" used to check the
modification between my w.c. to the externals explicit revision.
When using svn1.8+ the same command checks the modification between my w.c. and
the external HEA
> -Original Message-
> From: Stefan [mailto:luke1...@gmx.de]
> Sent: dinsdag 11 februari 2014 22:07
> To: users@subversion.apache.org
> Subject: how to use one bug ID syntax for two different butracking-pools
>
> Hi,
>
> I'm not sure whether TSVN mailing list would be more appropriate f
You needn't dump/load.
Just run svn propget --revprop svn:log -r$N URL > r$N.log in a for loop
running from 0 to HEAD.
Run your sed script on all the files.
Then svn propset --revprop -r$N svn:log -F r$N.log in a similar for loop.
Regards,
Arwin Arni
On Wed, Feb 12, 2014 at 2:36 AM, Stefan
Hi,
I have a problem with the svn:global-ignore property.
I would like to recursively ignore all subfolders named "bin". When I set this
property on a folder "foo" and then add a folder "foo/bin" it is working. But
when I create a folder "foo/bar/bin" the "bin" isn't ignored cause the folder
"
Spiegel Tal writes:
> I'm using in my project externals set to explicit revision.
>
> When using svn1.7+ the command "svn status -v -u" used to check the
> modification between my w.c. to the externals explicit revision.
>
> When using svn1.8+ the same command checks the modification between my
>> -Original Message-
>> From: karl.mau...@gmx.de [mailto:karl.mau...@gmx.de]
>> Sent: dinsdag 11 februari 2014 14:33
>> To: users@subversion.apache.org
>> Subject: Pre commit script exit code validation stopped working after
>> subversion update
>>
>> Hello,
>>
>> we just tried to update
Hi Philip,
I didn't make myself clear.
I've encounter the problem when using svn1.8+ client and svn1.7+ server.
When I used to work with a svn1.7 client against svn1.7 server there was no
mismatch with the externals status comparison.
Can you approve this is a bug within the svn1.8+ client? It
Spiegel Tal writes:
> I didn't make myself clear.
> I've encounter the problem when using svn1.8+ client and svn1.7+ server.
>
> When I used to work with a svn1.7 client against svn1.7 server there was no
> mismatch with the externals status comparison.
>
> Can you approve this is a bug within t
Does anyone know what this error means and how I can correct it?
svn: E22: /.subversion/config:93: Option expected
I am getting this message while trying to browse the SVN repos from a build
server. This was working fine a few days ago (when I last accessed the repo
from this server).
My SVN
For what it's worth, line 93 refers in the config file is listed below. As
far as I know, this file hasn't been modfied recently by anyone. At least
that's what my team members tell me.
92 ### put last-committed timestamps on every file touched.
93 use-commit-times = yes
94 ### Set no-unlo
On 2014-02-12 11:46 AM, C M wrote:
For what it's worth, line 93 refers in the config file is listed
below. As far as I know, this file hasn't been modfied recently by
anyone. At least that's what my team members tell me.
92 ### put last-committed timestamps on every file touched.
93 use-
Peter Döhler writes:
> I have a problem with the svn:global-ignore property.
'svn:global-ignore' should be 'svn:global-ignores'. Is that your
problem? The standard 1.8 client will warn you if you try to set the
mispelled 'svn:global-ignore' on a working copy. If you didn't see a
warning then
12 matches
Mail list logo
