Browse Source Remove references to the patchwork server.

Bastien Guerry 6 years ago
1 changed files with 1 additions and 21 deletions
  1. 1 21

+ 1 - 21

@@ -134,26 +134,6 @@ When sending a patch (either using =git diff= or =git format-patch=) please
 *always add a properly formatted Emacs ChangeLog entry*.  See [[id:c526dfd7-2b0c-4b66-9deb-6e442e48708c][this section]]
 for details on how to create such a ChangeLog.
-** Patches get caught on patchwork
-As long as these patches are formatted properly, they will be automatically
-registered at [[][John Wiegley's patchwork server]] and will then be accepted,
-rejected, or sent back to the author with a request for modification.
-Patchwork assumes there is *only one patch per email* and will not catch
-more than one patch -- so please send multiple patches in separate emails.
-In this context, "formatted properly" means that the patches are included
-either plainly in the mail text, or as text attachments (mime-type text,
-subtypes "x-patch", "x-diff", or "plain").  In particular, binary types or,
-even worse, "application/octet-stream" (the asinine default of some mail
-programs) are *not* going to be recognized.  Please find out how to
-convince your mail program to send proper attachments.  Also, if you
-include the patch inline, please make sure that your mail program does not
-reformat it (although there are plenty of places further down the line
-where that can happen, unfortunately). If you attach the patch, then
-reformatting is not a problem.
 ** Sending commits
 For every patch you send, we suggest to use =git format-patch=.
@@ -177,7 +157,7 @@ Here is the suggested workflow:
 :   ~$ git format-patch master             # Creates two patches
   ... Then two patches for your two commits are ready to be sent to the
-  list and detected by the patchwork server.
+  list.
 Write useful commit messages: please provide 1) a reason for it in your