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

Re: Blocking svn:mergeinfo?

From: Tyler Roscoe <tyler_at_cryptio.net>
Date: Mon, 12 Oct 2009 14:53:57 -0700

On Mon, Oct 12, 2009 at 01:56:14PM -0700, Kylo Ginsberg wrote:
> I got a proposal today that we block svn:mergeinfo in a pre-commit
> hook for a sub-tree of a repository (a completely self-contained
> sub-tree, i.e. including trunk and all feature/release branches for a
> particular project).
>
> I said that the downsides would be:
> * 1.5+ clients must specify --ignore-ancestry for all 'svn merge' commands
> * clients must use 1.4-style merges, e.g. fully specify revision
> ranges, don't use --reintegrate
> * clients won't see merge info in log/annotate operations, e.g. with a
> 'svn merge log -g'

Sounds like a bad idea to me. svn 1.5-style merge tracking works very
well. What is the actual problem you (they?) are trying to solve?

tyler

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2406811

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-13 23:14:33 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.