(see also [wiki:PatchReviewProcess How To Review Patches])

Please create a new ticket to track the issue unless your patch is a patch for an issue that is already ticketed.

Then get a darcs repository which has the current trunk in it. You can do this by running {{{darcs get --lazy http://tahoe-lafs.org/source/tahoe-lafs/trunk pristine}}}, which makes a new subdirectory of the current directory whose name is {{{pristine}}} and which contains a copy of the current trunk.

Then cd into the pristine directory and pull the patch you've written into it (this may require other patches which your patch depends on to come along for the ride—that's okay).

Then run the following darcs commands to generate a darcs patch file named {{{WHAT.darcs.patch}}}:

{{{
  darcs record
  darcs send -o WHAT.darcs.patch
}}}

(The name of the file, which is given here as {{{WHAT.darcs.patch}}}, is not that important. Use a relevant word or two or maybe the ticket number.)

Write a descriptive patch name and description like these ones (the "patch name" and "patch description" are labelled on these pages as "Message"): [changeset:8ba536319689ec8e], [changeset:1de4d2c594ee64c8], [changeset:d0706d27ea2624b5], [changeset:63b28d707b12202f], [changeset:c18b934c6a8442f8], [changeset:7cadb49b88c03209], [changeset:be6139dad72cdf49].

And attach it to the ticket.

Please use a filename like {{{*.darcs.patch}}} so that Trac will display it with proper syntax highlighting.

Or without darcs you can attach a normal old unified diff. If you do that, please use a filename like {{{*.patch}}} so that Trac will display it with syntax highlighting. (If using darcs, you can generate a unified diff with {{{darcs whatsnew --unified}}}.)