Trac formatting

Simon Marlow marlowsd at
Wed Nov 13 10:36:13 UTC 2013

On 12/11/13 15:53, Joachim Breitner wrote:

> Am Dienstag, den 12.11.2013, 15:24 +0000 schrieb Simon Peyton-Jones:
>> When Trac formats commit messages it is doing a terrible job.  See for
>> example:
>> The commit message is nigh illegible until typeset without makup (see
>> comment 10).
> I believe it is a feature, not a bug: Trac encourages you to use
> markdown markup (which supposedly looks good also in plain text) in your
> commit messages. This not only makes them look nice, provides additional
> features like automatic linking (compare the reference to #5996 in
> comment 9 and comment 10).
> In this case the tables should have been indented by 4 spaces, or
> surrounded by {{{..}}}, in the commit message to make it come out
> nicely.
> Whether this is desirable is a different question. I like it, but the
> heavy users of the repository and trac need to decide what they prefer –
> the ability to use markup in the commit messages, or the freedom to do
> any kind of ascii art.

I'm with Simon on this one.  I much preferred the old plain-text 
rendering of commit messages.

I don't want to start using a particular markup format (which is not 
markdown, it's Trac's own format AIUI) in our commit messages.  What 
happens if we switch from Trac to something else in the future?


More information about the ghc-devs mailing list