From: Jim Blandy <jimb@codesourcery.com>
To: fnf@specifix.com
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Spelling fixes
Date: Tue, 23 May 2006 00:21:00 -0000 [thread overview]
Message-ID: <vt21wul8xe7.fsf@theseus.home.> (raw)
In-Reply-To: <200605191646.22730.fnf@specifix.com> (Fred Fish's message of "Fri, 19 May 2006 16:46:22 -0400")
Fred Fish <fnf@specifix.com> writes:
> Checked in under the 'obvious fix rule', though not sure if current
> practice is to record in ChangeLog or not.
>
> 2006-05-19 Fred Fish <fnf@specifix.com>
>
> * Makefile.in: Fix spelling of 'explicitly' and 'explicit'.
> * dwarfread.c: Fix spelling of 'unexpected'.
> * mips-tdep.c: Fix spelling of 'possible' and 'Determine'.
> * stack.c: Fix spelling of 'RETURN_VALUE'.
Obvious changes to comments just need a log entry saying 'Doc fixes.'
prev parent reply other threads:[~2006-05-22 23:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-20 0:27 Fred Fish
2006-05-23 0:21 ` Jim Blandy [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=vt21wul8xe7.fsf@theseus.home. \
--to=jimb@codesourcery.com \
--cc=fnf@specifix.com \
--cc=gdb-patches@sourceware.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