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

Re: svn 1.5 merge -c revision and svn diff/log confusion

From: Stein Somers <ssomers_at_opnet.com>
Date: Fri, 30 Oct 2009 16:33:07 +0100

Karol Szkudlarek wrote:
> Maybe developers of subversion should write
> that 1.5.x is not recommended for using in
> a production system.

If you're looking for perfect software, you'll have to write it yourself. The
spuriously generated mergeinfo is a minor little bug that you can easily work
around. Your data is safe, nothing crashes, nothing hangs.

I'm not even sure it is a bug at all. It may be something dummies like us do
wrong. Like commit, forget to update, merge. Or resolve a conflict in some
unintended way. But at least one other list member has mentioned it's a bug.
And it never happens in the production environment I work in since svn 1.6.

Bob Archer wrote:
> 1. The merge data doesn't hurt anything

People are confused and write to the list, so some merge data is hurting them
a little.

> if you merge from the root project folder the merge info won't propagate

The heart of the thread is that this is not true for some 1.5 version(s):
some children get (initially empty) explicit mergeinfo attributes, out of the

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-30 16:34:12 CET

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