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

new and easier! 

[Imported from Trac: page Patches, version 6]
zooko 2009-06-16 23:12:02 +00:00
parent b1282bebfb
commit 8bbf1473b3
1 changed files with 4 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
Patches.md

@ -1,25 +1,11 @@
UPDATE, now that we have automatic mail from trac to tahoe-dev, maybe it would be better to attach patches to trac. Please create a new ticket to track the issue unless your patch is a patch for an issue that is already ticketed.
On the [/cgi-bin/mailman/listinfo/tahoe-dev tahoe-dev mailing list], Zooko suggests: Then run the following darcs command to generate a darcs patch file:
> I really like using the mailing list for patches, because the mailing
> list is a public, on-the-record conversation that includes everyone.
> What about this:
``` ```
darcs send -o patch.darcspatch darcs send -o patch.darcspatch
bzip2 patch.darcspatch
darcs diff -u -p"${PATCHRE}" > patch.diff.txt
``` ```
> and then send both to the mailing list as attachments. This is more And attach it to the ticket.
> work for the submitter, as they have to attach the files to a message
> and send the message (instead of allowing "darcs send" to send the
> message for them).
> The bzip2 is necessary to prevent various mail software from mangling the patch so it can't be applied. If you don't have darcs or don't want to use it, just attach a normal old diff.
> The good things about this are:
* 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.