[Imported from Trac: page Patches, version 27]

Zancas 2011-08-10 16:35:40 +00:00
parent d7bfdbcc86
commit 088d2f4628

@ -12,8 +12,9 @@ Then run the following darcs commands to generate a darcs patch file named `WHAT
(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.) (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. 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.
If, and only if, a single file was modified in the patch it is conventional to begin the "patch name" field with "<FILENAME>:"
And attach it to the ticket. Attach the patch to the ticket.
Please use a filename like `*.darcs.patch` so that Trac will display it with proper syntax highlighting. Please use a filename like `*.darcs.patch` so that Trac will display it with proper syntax highlighting.