Re: [Issue 3312] New - "Mergeinfo for '...' maps to an empty revision range" due to sparse merging

Hello,
please consider fixing this defect or providing a workaround before 1.6,
because once the merge info of a repository gets into the state that causes
the problem, there is no simple way to fix the repository. Making a reverse
merge of the revision that caused it does not help.
As long as the problematic revision retains in the repository, merging and
log -g do not work.

Thanks,
Arcady.

-- 
View this message in context: http://www.nabble.com/-Issue-3312--New---%22Mergeinfo-for-%27...%27-maps-to-an-empty-revision-range%22-due-to-sparse-merging-tp20342148p20359441.html
Sent from the Subversion Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org