On Sat, Aug 09, 2008 at 02:34:48PM -0400, Max Battcher wrote: > David, is there any reason to think that a context file generated with a > darcs 1 repository would _not_ be compatible when using darcs get > --context against a darcs 2 format repository?
I'm not David, and I don't fully understand what I'm talking about here, but I very much suspect the way 'darcs convert' flattens mergers can change the dependencies in the converted repo in a way that it is not possible to pull the same subsets of patches from it. > Then once a super-branch is converted it becomes a simple matter to > recreate branch1: > > $ darcs get --context branch1.context super-branch branch1 I tried this on a repo of mine. First, I could not pull all patches into the super-branch because of exponential conflicts, so I skipped one branch all together, and unpulled the troublesome patches in the other branches. Secondly, I was unable to reconstruct all the branches after conversion. 'darcs get' complained about something couldn't commute, and the resulting repos, although fine with 'darcs check', didn't contain all expected patches. One of them only contained two patches instead of expected six hundred. I it possible that a repeated 'darcs pull' into empty repos would have been more successful, but pulled some extra depended upon patches. I didn't try this. I suspect the number of unwanted patches would have be high because I had many conflicts between the different branches. I don't want to discourage anyone. I did pick a repo that I knew would be tricky, just to support my suspicion that this was not guaranteed to succeed. I have some faith that a super-branch where there are no branch-to-branch conflicts might be guaranteed to succeed. -- Tommy Pettersson <[EMAIL PROTECTED]> _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
