https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107297
--- Comment #7 from Jonathan Wakely ---
(In reply to Andrew Pinski from comment #3)
> And many folks don't use markdown especially when they are used to plain
> text. C++ is the worst where < gets eaten up. This has been one of issues
> with git
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107297
--- Comment #6 from Jonathan Wakely ---
(In reply to Eric Gallager from comment #2)
> I would also want comments to be editable if this gets turned on, in case I
> screw up my formatting... is there a way to allow that in bugzilla?
There's a Pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107297
--- Comment #5 from Jeff Muizelaar ---
(In reply to Eric Gallager from comment #2)
> I would also want comments to be editable if this gets turned on, in case I
> screw up my formatting... is there a way to allow that in bugzilla?
bugzilla.mozi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107297
--- Comment #4 from Andrew Pinski ---
Being able to mark a comment or otherwise as not markdown is needed as all old
comments will be messed up that way.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107297
--- Comment #3 from Andrew Pinski ---
I think for gcc I rather not support markdown because source gets mangled if
not enclosed with ' or '''.
And many folks don't use markdown especially when they are used to plain text.
C++ is the worst where
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107297
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
--- Commen
