es you to keep track of the number of the revision
> number the v3 branch was last synced up to (r70081 in this example).
Of course, but it's tedious and error prone. We'll only use that if we can't
find a better solution which properly tracks the mergeinfos.
--
Eric Estievenart
ncestry
svn: E24: Cannot merge automatically while ignoring mergeinfo
We'll continue our investigations, and keep you updated.
Thanks
--
Eric Estievenart
Hello there (and congrats for the release !),
I was about to directly file a bug but finally decided to go through the proper
process...
As we are planning to move from 1.7 to 1.8, we already migrated a few clients
(not yet the server), and the following change, as I suspected, hit us:
* reject
