On Mon, Nov 10, 2008 at 01:27:21PM -0800, Jason Dagit <[EMAIL PROTECTED]> wrote: > The latter behaviour sounds like darcs to me. So, if there is a bug > it's one of the following: > 1) The current UI is "correct" but has unexpected behaviour; > 2) The manual needs to clarify. > > The idea is that if you want a patch and applying it to the target > repo requires some other patch (the dependency) then darcs doesn't > want to give you the patch without its dependencies. That's because > without the dependency you can't safely apply the patch. > > This is actually another case where scripts that strip out patches and > send them by themselves would be buggy. > > On second read, I think the quoted bit from the manual is well > intentioned it's just not clear. As in one interpretaton of not > automatically fulfilling dependencies is that it doesn't generate the > bundle because it didn't workout the deps? Clearly this is ambiguous > and should be updated. > > I hope that help!
First, thanks for clarifying. Second, I just realised that given I "export" all the patches based on the darcs changes --xml output, in fact I never get multiple patches exported, so the good soltuion for my problem was a simple: darcs send -a -o foo.dpatch --matches='hash bar.gz' /path/to/other/repo Thanks!
pgpnfhX43spN2.pgp
Description: PGP signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
