suggest thing.darcs.patch per david-sarah's observation that .darcspatch.txt doesn't trigger syntax highlighting
[Imported from Trac: page Patches, version 19]
parent
405195035e
commit
02a817e47d
|
@ -2,17 +2,17 @@
|
|||
|
||||
Please create a new ticket to track the issue unless your patch is a patch for an issue that is already ticketed.
|
||||
|
||||
Then run the following darcs commands to generate a darcs patch file named `WHAT.darcspatch.txt`:
|
||||
Then run the following darcs commands to generate a darcs patch file named `WHAT.darcs.patch`:
|
||||
|
||||
```
|
||||
darcs record
|
||||
darcs send -o WHAT.darcspatch.txt
|
||||
darcs send -o WHAT.darcs.patch
|
||||
```
|
||||
|
||||
Please write a descriptive patch name and description like these ones: 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 `*.darcspatch.txt` 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.
|
||||
|
||||
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`.)
|
Loading…
Reference in a new issue