TortoiseSVN 1.7.3 released
Stefan Küng <[email protected]> Fri, 16 Dec 2011 19:09:26 +0100
| Newsgroups | gmane.comp.version-control.subversion.tortoisesvn.announce,gmane.comp.version-control.subversion.tortoisesvn.user |
|---|---|
| Message-ID | <[email protected]> |
Hi,
I'm happy to announce the release of TortoiseSVN 1.7.3. It is still
linked against the SVN 1.7.2 library.
Due to some nasty bugs in TortoiseSVN 1.7.2 which in some specific
situations could make it crash, we're releasing this version out of sync
with SVN releases.
TortoisePlink was also updated to Plink 0.62 which had a security issue
fixed.
You can download it from here:
http://tortoisesvn.net/downloads.html
The changelog for 1.7.3:
Version 1.7.3
- BUG: Issue #149: Crash in OpenSSL. (Stefan)
- BUG: Issue #150: Repobrowser: Don't show
externals in checkout selection mode . (Stefan)
- BUG: Issue #152: log crashes with too
many bugtrack links. (Stefan)
- BUG: Issue 155: crash when accessing a server with
an invalid ssl certificate. (Stefan)
- BUG: Issue #156: subdir within WC not
recognized as WC. (Stefan)
- BUG: Issue #157: Title Bar not updating with
currently viewed repository. (Stefan)
- BUG: Issue #158: IBugTraqProvider2 CheckCommit
returns a relative commonURL. (Stefan)
- BUG: Issue #159: folder browse dialog can be
closed with invalid paths. (Stefan)
- BUG: Issue #160: Repo browser shows
incorrect contents for directories
that differ only by case. (Stefan)
- NEW: Issue #113: Option to turn off pre-fetching
and external parsing in repo browser. (Stefan)
- BUG: Issue #161: repo browser shows invalid
commands for the root. (Stefan)
- BUG: Line wrapping problems in Log
Messages dialog. (Stefan)
- BUG: Issue #166: TortoiseMerge slow with
long lines. (Stefan)
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=755&dsMessageId=2894036
To unsubscribe from this discussion, e-mail: [[email protected]].