public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jmuizelaar at mozilla dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/107297] Support markdown in bugzilla comments
Date: Wed, 19 Oct 2022 01:34:12 +0000	[thread overview]
Message-ID: <bug-107297-4-C9qjucixwI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107297-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107297

--- Comment #5 from Jeff Muizelaar <jmuizelaar at mozilla dot com> ---
(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.mozilla.org supports editing comments. I'm not sure if it's supported
in stock Bugzilla.

(In reply to Andrew Pinski from comment #4)
> Being able to mark a comment or otherwise as not markdown is needed as all
> old comments will be messed up that way.

When bugzilla.mozilla.org enabled this, old comments were kept as plain text.


That being said, I asked about how Markdown is implemented in
bugzilla.mozilla.org:

jrmuizel:
> How is bmo's Markdown support implemented?
> Is it easy for other bugzilla instances to turn on Markdown?
glob:
It was a lot of work to implement it.  bugzilla.mozilla.org is very different
from stock Bugzilla, it won't be easy to bring to other instances.  I believe
there are plans to switch stock Bugzilla to follow BMO, but we're not directly
involved in that.

So perhaps this is not as easy to enable as I thought it would be.

  parent reply	other threads:[~2022-10-19  1:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17 13:30 [Bug other/107297] New: " jmuizelaar at mozilla dot com
2022-10-17 13:33 ` [Bug other/107297] " marxin at gcc dot gnu.org
2022-10-19  0:46 ` [Bug web/107297] " egallager at gcc dot gnu.org
2022-10-19  0:59 ` pinskia at gcc dot gnu.org
2022-10-19  1:01 ` pinskia at gcc dot gnu.org
2022-10-19  1:34 ` jmuizelaar at mozilla dot com [this message]
2022-10-19 10:51 ` redi at gcc dot gnu.org
2022-10-19 11:02 ` redi at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-107297-4-C9qjucixwI@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).