Hello!
To reproduce (if possible), I did the following:
- SVN server V1.6 (not sure what version exactly, I don't have direct
access to the server, but it's a rather uptodate 1.6 version).
- TortoiseSVN is used to access the server. This used to be V1.6.17.
- I just updated TortoiseSVN to V1.7.0
It's me again, I have some additional information regarding the problem, maybe
this helps:
> -Ursprüngliche Nachricht-
> Von: Brockamp, Peter
> Gesendet: Montag, 17. Oktober 2011 17:49
> An: 'users@subversion.apache.org'
> Betreff: Supposed serious(
chricht-
> > Von: Brockamp, Peter
> > Gesendet: Montag, 17. Oktober 2011 17:49
> > An: 'users@subversion.apache.org'
> > Betreff: Supposed serious(?) bug in either subversion or
> > TortoiseSVN when upgrading to latest V1.7.0 version
>
> - I checked and
On Mon, Oct 17, 2011 at 06:16:45PM +0200, Brockamp, Peter wrote:
> So, as I see it now, this is in fact a *serious* problem at least with
> TortoiseSVN
> 1.7.0 working against an 1.6 SVN-server! So actually I must severly warn
> about using
> this configuration in a production environment, it wil
Hello, thx for the quick answer!
> -Ursprüngliche Nachricht-
> Von: Stefan Sperling [mailto:s...@elego.de]
> Gesendet: Dienstag, 18. Oktober 2011 11:20
> An: Brockamp, Peter
> Cc: users@subversion.apache.org
> Betreff: Re: Supposed serious(?) bug in either subversion
Hello,
> -Ursprüngliche Nachricht-
> Von: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
> Gesendet: Dienstag, 18. Oktober 2011 08:44
> An: Brockamp, Peter
> Cc: users@subversion.apache.org
> Betreff: Re: Supposed serious(?) bug in either subversion or
> Tortoise
On Tue, Oct 18, 2011 at 12:53:14PM +0200, Brockamp, Peter wrote:
> However, I had to learn the problem was reported by lots of other
> people before. Sorry about being the zillionth re-reporting this issue.
>
> http://subversion.apache.org/mailing-lists.html#list-list
> talks about searching the a
