On Tue, Jan 18, 2011 at 1:04 AM, Sittampalam, Ganesh <ganesh.sittampa...@credit-suisse.com> wrote: > > The output of darcs send should always work fine with the target repo > (or any repo that's a superset of that). > > I guess the problem is that people are trying to use it with other > repositories that are missing patches that are in the target repo.
That's not what's happening. We have a canonical central trunk repository -- http://tahoe-lafs.org/source/tahoe-lafs/trunk . Then developer A has their local repo which has all of trunk, plus patches 1, 2, 3. Developer A runs "darcs send", selecting patch 3 to send. Darcs does not insist on sending patches 1 or 2 since they are independent of 3. Then Developer B tries to "darcs apply" the resulting file, to their copy of trunk, and they get an error message saying that the patch 3 can't be applied since they lack patches 1 and 2. The work-around that we settled on was that Developer A, when they want to send patch 3, first creates a new copy of trunk, then pulls patch 3, but not patches 1 or 2 into that copy, then runs "darcs send". Regards, Zooko _______________________________________________ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
