On 06/20/2013 09:24 AM, Johan Corveleyn wrote:
> I think this is an important change (improvement) that deserves
> mention in the release notes, rather than being burried in the huge
> CHANGES list. WANdisco even put it in their announcement mail
> "WANdisco offers Apache Subversion 1.8" (as one of five items they
> considered important enough to mention explicitly).
> Just my 0.02 €
Let's evaluate the change on its own merits, please, not on the basis of
some company's marketing fluff. It's not uncommon in press releases to see
even the littlest things billed as more world-changing than they really are,
and I daresay WANdisco's Marketing folks aren't unique in this respect.
I agree that the feature is a good one to highlight. Top 5 in the release?
Puh-lease. But it certainly deserves a release note mention, if only
because it's a behavior change that someone might be counting on continuing
to work. Maybe they created a branch in the past as a parallel import
instead of via the 'svn copy' construct, and have been merging just fine
between that branch and another -- in 1.7, that seems to have worked fine:
$ svn export A Z
$ svn add Z
$ svn ci -m ""
Transmitting file data ...........
Committed revision 2.
$ echo "foo" >> A/mu
$ svn ci -m ""
Transmitting file data .
Committed revision 3.
$ svn merge ^/A Z
--- Merging r2 through r3 into 'Z':
--- Recording mergeinfo for merge of r2 through r3 into 'Z':
$ svn diff
--- Z (revision 1)
+++ Z (working copy)
Property changes on: Z
--- Z/mu (revision 2)
+++ Z/mu (working copy)
@@ -1 +1,2 @@
This is the file 'mu'.
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Enterprise Cloud Development
Received on 2013-06-20 16:54:23 CEST