Hi,
sorry...ignore the last patch i sent there was a wrong release date for
1.6.12 ...;-(
Attached a new one..
Sorry..
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
Index: publish/docs/release-notes/release-history.html
===================================================================
--- publish/docs/release-notes/release-history.html (revision 956647)
+++ publish/docs/release-notes/release-history.html (working copy)
@@ -31,6 +31,12 @@
<ul>
<li>
+ <b>Subversion 1.6.12</b> (Monday, 21 June 2010): Bugfix release.
+ </li>
+ <li>
+ <b>Subversion 1.6.11</b> (Friday, 16 April 2010): Bugfix release.
+ </li>
+ <li>
<b>Subversion 1.6.9</b> (Monday, 25 January 2010): Bugfix release.
</li>
<li>
Index: publish/docs/release-notes/1.2.html
===================================================================
--- publish/docs/release-notes/1.2.html (revision 956647)
+++ publish/docs/release-notes/1.2.html (working copy)
@@ -60,7 +60,7 @@
</ul>
<p>For binary packages, please see <a
-href="getting.html#binary-packages">the binary package
+href="/packages.html">the binary package
list</a>. Note that binary packages usually come out about a week
after the corresponding source release. The package maintainers are
volunteers, so please don't harass them — they know
Index: publish/docs/release-notes/1.3.html
===================================================================
--- publish/docs/release-notes/1.3.html (revision 956647)
+++ publish/docs/release-notes/1.3.html (working copy)
@@ -60,7 +60,7 @@
</ul>
<p>For binary packages, please see <a
-href="getting.html#binary-packages">the binary package
+href="/packages.html">the binary package
list</a>. Note that binary packages usually come out about a week
after the corresponding source release. The package maintainers are
volunteers, so please don't harass them — they know
@@ -147,7 +147,7 @@
part of some other change pulled down via an OS package delivery
mechanism — for example, upgrading one's Subversion
package. If this happens to you, you will need
-to <a href="faq.html#bdb43-upgrade">upgrade existing BerkeleyDB-based
+to <a href="/faq.html#bdb43-upgrade">upgrade existing BerkeleyDB-based
repositories to 4.3.</a></p>
<p>Since Subversion 1.2, the <a
Received on 2010-06-21 19:32:22 CEST