[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Svn 1.4 -> 1.5 upgrade

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Sat, 31 May 2008 23:33:27 -0400

Miha Vitorovic <mvitorovic_at_nil.si> writes:
> Thank you Karl an Mark for the info. I'm not sure I will test the 1.5 ->
> 1.4 transition, there just isn't enough time.
> But, I do have another question: We didn't have much need for branching
> and merging until recently, but now we have a project where it is the
> norm. We have created two "branches" of the trunk already (they are more
> of a beta and release branch, actually), so the they will remain
> "permanent", and the trunk will be continuously merged into them. So, my
> question is, will these two "branches" automagically receive merge info
> when I upgrade the server, or is there something special I need to do
> (maybe delete and recreate them?).

Well, we'd need to know more details before saying for sure, but see
(it may answer your question).

Upgrading the server will *not* automatically go back and add the
svn:mergeinfo property to any old revisions. This has various
implications, most of which don't seem to be documented well enough in
the Release Notes :-). We'd like to improve that, and understanding
your scenario may help us do so...


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-01 05:33:49 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.