public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [sim] Fix pervasive typo
Date: Mon, 1 Jan 2024 10:47:17 -0500	[thread overview]
Message-ID: <ZZLehVeQV60tF0zy@vapier> (raw)
In-Reply-To: <20231231215558.1142220-1-tom@tromey.com>

[-- Attachment #1: Type: text/plain, Size: 405 bytes --]

On 31 Dec 2023 14:55, Tom Tromey wrote:
> I noticed a typo in a sim constant.  This patch fixes it.

thanks, applied with some commit fixes:
* using [tag] in the subject line breaks `git am` which is why `git:` is better
* added the actual typo being fixed to the message

fwiw, much of the common/ logic comes from the ppc/ tree which is why a lot of
logic, and typos, get duplicated between them.
-mike

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2024-01-01 15:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-31 21:55 Tom Tromey
2024-01-01 15:47 ` Mike Frysinger [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=ZZLehVeQV60tF0zy@vapier \
    --to=vapier@gentoo.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.com \
    /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).