From: Jim Garrison <jim.garrison@troux.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Rolling back to 1.6.x Subversion
Date: Wed, 16 Nov 2011 23:06:00 -0000 [thread overview]
Message-ID: <D0CBCC01C005D44CB4009B8A6B532BE41F0B731B@IAD2MBX11.mex02.mlsrvr.com> (raw)
> -----Original Message-----
> On Behalf Of Jeremy Bopp
> Sent: Wednesday, November 16, 2011 9:18 AM
> Subject: Re: Rolling back to 1.6.x Subversion
>
> That whole process is going to be unsupported here though, so is there
> some reason you must remain on such an old release of subversion?
Um... 1.7 just came out in the last few months, 1.6.17 isn't "such an old
release". Consider users who depend on clients (SVNKit) that don't
yet have 1.7 native support (i.e. Subclipse). We have to stay on
1.6 until ALL our clients support 1.7 due to the working copy
restructuring. When 1.7 came out I saved a copy of the 1.6.17
distribution locally.
--
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
next reply other threads:[~2011-11-16 23:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 23:06 Jim Garrison [this message]
2011-11-17 0:53 ` Jeremy Bopp
2011-11-17 7:50 ` Andrey Repin
2011-11-17 15:37 ` Jeremy Bopp
2011-11-17 16:10 ` Jon Clugston
2011-11-17 16:47 ` Jeremy Bopp
2011-11-17 19:05 ` Andrey Repin
2011-11-17 9:10 ` Andy Koppe
2011-11-17 11:12 ` Csaba Raduly
2011-11-17 16:33 ` Jeremy Bopp
2011-11-17 19:05 ` Andrey Repin
-- strict thread matches above, loose matches on Subject: below --
2011-11-15 21:47 Sean LeBlanc
2011-11-16 15:18 ` Jeremy Bopp
2011-11-16 21:16 ` David Rothenberger
2011-11-16 22:35 ` Andrey Repin
2011-11-16 23:01 ` David Rothenberger
2011-11-17 19:06 ` Warren Young
2011-11-17 22:50 ` Andrey Repin
2011-11-18 0:14 ` Warren Young
2011-11-18 9:50 ` Andrey Repin
2011-11-18 14:25 ` Csaba Raduly
2011-11-18 17:23 ` Dave Korn
2011-11-19 9:30 ` Warren Young
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D0CBCC01C005D44CB4009B8A6B532BE41F0B731B@IAD2MBX11.mex02.mlsrvr.com \
--to=jim.garrison@troux.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).