[Imported from Trac: page Patches, version 2]
parent
56aa12ecc6
commit
ec481a658f
12
Patches.md
12
Patches.md
|
@ -5,14 +5,16 @@ On the [/cgi-bin/mailman/listinfo/tahoe-dev tahoe-dev mailing list], Zooko sugge
|
|||
|
||||
> What about this:
|
||||
|
||||
> darcs send -o patch.darcspatch
|
||||
> darcs diff -u -p"${PATCHRE}" > patch.diff.txt
|
||||
```
|
||||
darcs send -o patch.darcspatch
|
||||
darcs diff -u -p"${PATCHRE}" > patch.diff.txt
|
||||
```
|
||||
|
||||
> and then send both to the mailing list as attachments? This is more
|
||||
> 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 good things about this are (a) hopefully everyone can see the
|
||||
> patch contents in-line in the mail and (b) you can add a "cover
|
||||
> letter" -- a message to the mailing list about the patch.
|
||||
> 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.
|
Loading…
Reference in a new issue