This is the mail archive of the
mailing list for the Cygwin project.
Re: : Subversion packages
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: Kevin Connor Arpe <kevinarpe at gmail dot com>, cygwin at cygwin dot com
- Date: Sun, 17 Nov 2013 22:48:23 +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>
- Reply-to: Andrey Repin <cygwin at cygwin dot com>
Greetings, Kevin Connor Arpe!
> Subversion version series are important because local repositories
> created by each series (1.6.x, 1.7.x, 1.8.x) are incompatible. In
> short, if you do "svn checkout" with svn 1.6.x, you cannot do "svn
> update" with svn 1.7.x or 1.8.x. For a variety of reasons, at my
> office, I am forced to use svn 1.6.x series. This precludes me from
> using standard pre-built Cygwin packages for Subversion work. I'm
> always jumping back to a IDE or DOS box to manage my svn local repos.
I'm using native Subversion client. 1.6, yes.
For a simple fact I can't be arsed to launch svn tool each time I want to
know, if I'm located in working directory or not.
Do you have any hard reason to use Cygwin port?
Andrey Repin (firstname.lastname@example.org) 17.11.2013, <22:45>
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple