This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: : Subversion packages
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: David Stacey <drstacey at tiscali dot co dot uk>, cygwin at cygwin dot com
- Date: Mon, 18 Nov 2013 03:28:12 +0400
- Subject: Re: : Subversion packages
- Authentication-results: sourceware.org; auth=none
- References: <CAFMYRRMFGxJhMKNKVgUEs45Lb5dLCf-5vq+Rp5s0H=Eg1yB5kw at mail dot gmail dot com> <CAFMYRRPZWqSJWZVVGDQLLZ55ZOcD_H9q7UgPr4iZyKw9vr2TbQ at mail dot gmail dot com> <52890843 dot 90903 at acm dot org> <20131117194958 dot GA4006 at ednor dot casa dot cgf dot cx> <174472546 dot 20131118011119 at mtu-net dot ru> <52894C42 dot 3070704 at tiscali dot co dot uk>
- Reply-to: Andrey Repin <cygwin at cygwin dot com>
Greetings, David Stacey!
> Regarding you second point:
My second point is that I can't tell from looking at a directory, if I'm
inside a working copy or not. Launching any additional tools to do simple
telling is not an option.
This is a major drawback for me, and I'm not upgrading.
> The svn-1.7 client introduced a new working
> copy format, and you had to 'svn upgrade' your old svn-1.6 working
> copies. Once a working copy has been upgraded, it can then only be used
> with a svn-1.7 client. The same is true when upgrading the client from
> svn-1.7 to svn-1.8: the working copy must be upgraded again, and once
> upgraded the working copy can only be used with a svn-1.8 client. All of
> this is independent of the server version.
> In theory, it is possible for a svn-1.8 client to upgrade a svn-1.6
> working copy, although I've not attempted this personally.
--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 18.11.2013, <03:20>
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple