Changes between Version 5 and Version 6 of Patches


Ignore:
Timestamp:
2009-06-16T23:12:02Z (11 years ago)
Author:
zooko
Comment:

new and easier!

Legend:

Unmodified
Added
Removed
Modified
  • Patches

    v5 v6  
    1 UPDATE, now that we have automatic mail from trac to tahoe-dev, maybe it would be better to attach patches to trac.
     1Please create a new ticket to track the issue unless your patch is a patch for an issue that is already ticketed.
    22
    3 On the [/cgi-bin/mailman/listinfo/tahoe-dev tahoe-dev mailing list], Zooko suggests:
    4 
    5   I really like using the mailing list for patches, because the mailing
    6   list is a public, on-the-record conversation that includes everyone.
    7 
    8   What about this:
     3Then run the following darcs command to generate a darcs patch file:
    94
    105{{{
    116  darcs send -o patch.darcspatch
    12   bzip2 patch.darcspatch
    13   darcs diff -u -p"${PATCHRE}" > patch.diff.txt
    147}}}
    158
    16   and then send both to the mailing list as attachments.  This is more
    17   work for the submitter, as they have to attach the files to a message
    18   and send the message (instead of allowing "darcs send" to send the
    19   message for them).
     9And attach it to the ticket.
    2010
    21   The bzip2 is necessary to prevent various mail software from mangling the patch so it can't be applied.
    22 
    23   The good things about this are:
    24   * hopefully everyone can see the patch contents in-line in the mail, and
    25   * you can add a "cover letter" -- a message to the mailing list about the patch.
     11If you don't have darcs or don't want to use it, just attach a normal old diff.