public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "roland.illig at gmx dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109100] Possible typo CRS Date: Sat, 11 Mar 2023 06:04:33 +0000 [thread overview] Message-ID: <bug-109100-4-jusaA7CcVa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109100-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109100 --- Comment #1 from Roland Illig <roland.illig at gmx dot de> --- While here: In that same message, there is a single space between sentences 1 and 2, but 2 spaces between sentences 2 and 3. While here: can not is usually spelled cannot.
prev parent reply other threads:[~2023-03-11 6:04 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-11 6:01 [Bug target/109100] New: " roland.illig at gmx dot de 2023-03-11 6:04 ` roland.illig at gmx dot de [this message]
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-109100-4-jusaA7CcVa@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: linkBe 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).