[darcs-users] why does "darcs send" not do darcs's normalcherry-picking?

[Ian Lynagh]

On Sat, Feb 05, 2011 at 05:16:29AM -0700, Zooko O'Whielacronx wrote:
> On Tue, Jan 18, 2011 at 1:04 AM, Sittampalam, Ganesh
> <ganesh.sittampalam at 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.

If that's happening then it's a bug. Please file a ticket with a
testcase.


Thanks
Ian