tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

suggest bzip2 of darcs patches, to armor them against mangling in transit 

[Imported from Trac: page Patches, version 3]
zooko 2009-01-08 18:24:32 +00:00
parent 5756badb3f
commit d58e2f8a20
1 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
Patches.md

@ -7,6 +7,7 @@ On the [/cgi-bin/mailman/listinfo/tahoe-dev tahoe-dev mailing list], Zooko sugge
``` ```
darcs send -o patch.darcspatch darcs send -o patch.darcspatch
bzip2 patch.darcspatch
darcs diff -u -p"${PATCHRE}" > patch.diff.txt darcs diff -u -p"${PATCHRE}" > patch.diff.txt
``` ```
@ -15,6 +16,8 @@ On the [/cgi-bin/mailman/listinfo/tahoe-dev tahoe-dev mailing list], Zooko sugge
> and send the message (instead of allowing "darcs send" to send the > and send the message (instead of allowing "darcs send" to send the
> message for them). > message for them).
> The bzip2 is necessary to prevent various mail software from mangling the patch so it can't be applied.
> The good things about this are: > The good things about this are:
* hopefully everyone can see the patch contents in-line in the mail, and * hopefully everyone can see the patch contents in-line in the mail, and
* you can add a "cover letter" -- a message to the mailing list about the patch. * you can add a "cover letter" -- a message to the mailing list about the patch.