Hi darcs-users, I'm trying to learn more about how darcs force commutes work.
What I'd like to do is create a repository R1 with patches A and B, and then look at the patches that result if A and B get force-commuted. E.g. if I could pull just patch B and not A to a new repository, I think that would do the trick, but of course darcs pull won't let me do that because B depends on A. Question 1: Is there a simple way to make darcs do this? I can think of two complicated ways, which I might resort to: (a) Play with the darcs source code. (b) Set up contrived situations involving merges to force darcs to do the force-commutes I'm looking for. Question 2: Is there a way to make "darcs changes" show the patch contents? For now, I've been manually examining files in _darcs/patches. I vaguely remember there's an option to darcs changes or a related command to show the patch contents, but I can't seem to find it now. Thanks, James _______________________________________________ darcs-users mailing list darcs-users@osuosl.org https://lists.osuosl.org/mailman/listinfo/darcs-users
