On 2 Sep 2011, at 14:56, Eric Kow wrote: > I'm afraid the answer boils down to "don't do that" > (copy and paste patch bundles) > > On Fri, Sep 02, 2011 at 14:17:36 +0100, Ash Moran wrote: >> What is causing this? >> >> There are differences in whitespace but I don't know if they're >> significant. > > The differences in whitespace are indeed significant. In this > particular case, darcs parsed the bundle all the way to the bits > after 'Context: '. The file format uses an initial whitespace before > each line of the patch log, which avoids ambiguities stemming from patch > logs with things that look like the darcs file format.
Ahhh… I see what's happened now. Either on the sending or receiving side, Mail.app has removed the preceding whitespace before "Ignore-this:", and all the padding to separate out the +/- line prefix in the hunks. Does this mean you can't use `darcs send` directly with Mail.app? If not, this kinda spoils it for me, as otherwise it works like magic :-( > Entering thought experiment space: if by chance the Context was fine, > then (by rights) you should have be saved from applying a bad patch > through a patch bundle hash failure. If you defeated this by removing > the patch bundle hash, you might successfully apply the patches but then > run into trouble working with your collaborator later on because you > would have applied a subtly different patch but with the same id. > > So avoid copy+pasting, and while I'm at it, > don't fight the hash failures... :-) If I can't copy-paste, does that mean I always have to ask for patch bundles generated by `darcs send -o`? BTW, don't worry, I had no intention of even trying to fiddle with the hashes :) Cheers Ash -- http://www.patchspace.co.uk/ http://www.linkedin.com/in/ashmoran _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
