Blocking svn:mergeinfo?

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'

Does this sound correct? Any other downsides/gotchas? Anyone else
trying something like this?

Thanks,
Kylo

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

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-13 23:14:38 CEST