public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: David Rothenberger <daveroth@acm.org>
To: cygwin-announce@cygwin.com
Subject: Updated: subversion-1.7.14.-1
Date: Thu, 28 Nov 2013 05:00:00 -0000	[thread overview]
Message-ID: <5296CC31.60004@acm.org> (raw)

CYGWIN NEWS:
============
This release updates the older Subversion 1.7 series for those that
still need it. The new release includes some security fixes.

This is not the latest release of the subversion packages, so users
that want this will need to manually select this version in the
Cygwin installer.

NEWS:
=====
See CHANGES (URL below) for more information about the differences
between 1.7.0 and previous Subversion releases.

IMPORTANT: Please read the release notes (URL below) before
upgrading from a previous major release. 1.7 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.7.html

for more details about the changes in Subversion.

See

  http://svn.apache.org/repos/asf/subversion/tags/1.7.14/CHANGES

for more details about the changes in 1.7.14.

DESCRIPTION:
============
Subversion is a version control system designed to be a compelling
successor to CVS.

Please see 

  http://svnbook.red-bean.com/en/1.7/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

Wrinkles should merely indicate where smiles have been.
                -- Mark Twain

                 reply	other threads:[~2013-11-28  5:00 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=5296CC31.60004@acm.org \
    --to=daveroth@acm.org \
    --cc=cygwin-announce@cygwin.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).