From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 943993858C83; Wed, 19 Oct 2022 00:59:32 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 943993858C83 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1666141172; bh=iGAthqHxYXnkZX/iJc34qY+pA+rgII+rMBgutatOarA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=SAFT9jH20pX8zq/xzHrlcP2aC1K26aMEXE3iYRalOLli+AVnQjDsrTRntdwGyd3F4 wv/hO5U/xZVfdxzQ2N+9nBIHl6hRhlPkCjJvYzgyk6YgnwDtnBXy5Oube0k5+sI2FH cDv96zlu8SF3UMvW4JzoNugimabefl+UwXCcHYfw= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug web/107297] Support markdown in bugzilla comments Date: Wed, 19 Oct 2022 00:59:31 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: web X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107297 --- 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 te= xt. C++ is the worst where < gets eaten up. This has been one of issues with gi= thub even.=