From: David Rothenberger <daveroth@acm.org>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] Updated: subversion-1.8.19-1
Date: Mon, 14 Aug 2017 18:39:00 -0000 [thread overview]
Message-ID: <announce.cc3821b7-10a3-a956-7c81-0554eb23560c@acm.org> (raw)
NEWS:
=====
See CHANGES (URL below) for more information about the differences
between 1.8.0 and previous Subversion releases.
IMPORTANT: Please read the release notes (URL below) before
upgrading from a previous major release. 1.8 includes a new working
copy format with a manual upgrade operation. This will render your
working copy unusable with previous major releases. Furthermore,
there are some issues trying to upgrade corrupt working copies.
Please see the release notes
http://subversion.apache.org/docs/release-notes/1.8.html
for more details about the changes in Subversion.
See
http://svn.apache.org/repos/asf/subversion/tags/1.8.19/CHANGES
for more details about the changes in 1.8.19.
This release changes mod_dav_svn to no longer map requests to the local
filesystem. Administrators of mod_dav_svn servers should read the
section about this in the release notes:
http://subversion.apache.org/docs/release-notes/1.8.html#mod_dav_svn-fsmap
DESCRIPTION:
============
Subversion is a version control system designed to be a compelling
successor to CVS.
Please see
http://svnbook.red-bean.com/nightly/en/index.html
for the latest official release of the Subversion Book.
QUESTIONS:
==========
If you want to make a point or ask a question the Cygwin mailing list is
the appropriate place.
--
David Rothenberger ---- daveroth@acm.org
"Well hello there Charlie Brown, you blockhead."
-- Lucy Van Pelt
--
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
reply other threads:[~2017-08-14 18:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=announce.cc3821b7-10a3-a956-7c81-0554eb23560c@acm.org \
--to=daveroth@acm.org \
--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).