Stefan Sperling-7 wrote:
>
> It would be even nicer if Subversion had a way of guiding users to
> perform merges in accordance with a pre-defined strategy.
> So if the user tried to perform e.g. a cherry-picking merge to a branch
> for which cherry-picking isn't defined in the strategy, svn would error
> out and let the user know that this type of merge isn't allowed for the
> merge target.
>
This would be lovely, and is what we're aiming for using tortoise pre-commit
hooks and server hooks, although in a bit of a spit-and-sawdust way at the
moment.
> But of course, educating users is a social problem, not a technical one.
> No technical solution will ever solve this completely.
>
Totally agree... I think the problem needs to be tackled on both the social
and technical fronts. You can socialise it til the cows come home but it
only takes one user to ride rough-shod over your carefully defined merging
strategy because they need to commit urgently to cause many problems going
forward.
cheers, jamie
--
View this message in context:
http://old.nabble.com/how-to-find-out-from-where-a-file-has-been-copied-tp30725288p30727959.html
Sent from the Subversion Users mailing list archive at Nabble.com.
