public inbox for
 help / color / mirror / Atom feed
To: Jakub Jelinek <>,
Subject: Re: [committed] Fix comment typos
Date: Fri, 19 Jan 2024 22:14:10 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <Zaeqhb6NFEtVi3im@tucnak>


Just another commentary typo..

On 17 January 2024 11:23:01 CET, Jakub Jelinek <> wrote:

>--- gcc/	2024-01-03 11:51:23.314845233 +0100
>+++ gcc/	2024-01-16 18:56:57.383009291 +0100
>@@ -4718,8 +4718,8 @@ write_roots (pair_p variables, bool emit
> }
> /* Prints not-as-ugly version of a typename of T to OF.  Trades the uniquness
>-   guaranteee for somewhat increased readability.  If name conflicts do happen,



  reply	other threads:[~2024-01-19 21:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 10:23 Jakub Jelinek
2024-01-19 21:14 ` [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-07  7:11 Jakub Jelinek
2022-10-07 11:21 ` Jonathan Wakely
2007-11-14 13:10 Rask Ingemann Lambertsen

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:

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

  git send-email \ \ \ \ \

* 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).