From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [obvious] Fix typos in breakpoint.c and breakpoint.h
Date: Tue, 15 Feb 2011 18:24:00 -0000 [thread overview]
Message-ID: <AANLkTikOxy-VvzuH6++R60Rw1M1fX-T1sZzzrnC+M-gA@mail.gmail.com> (raw)
In-Reply-To: <1296840625.3204.1.camel@hactar>
On Fri, Feb 4, 2011 at 9:30 AM, Thiago Jung Bauermann
<bauerman@br.ibm.com> wrote:
> I just committed the following.
...
> 2011-02-04 Thiago Jung Bauermann <bauerman@br.ibm.com>
>
> Fix some typos.
> * breakpoint.c (update_watchpoint): Fix name of the
> update_global_location_list function.
> (print_one_breakpoint): Fix typo.
> (_initialize_breakpoint): Remove extra space in hbreak help
> string.
> * breakpoint.h (struct bp_location) <length>: Fix field
> description.
AFAICT, both above and subsequent change on 02/07 are missing from ChangeLog
Do obvious commits not require ChangeLog entries?
Thanks,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2011-02-15 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 17:31 Thiago Jung Bauermann
2011-02-15 18:24 ` Paul Pluzhnikov [this message]
2011-02-15 18:57 ` Tom Tromey
2011-02-15 19:30 ` Paul Pluzhnikov
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=AANLkTikOxy-VvzuH6++R60Rw1M1fX-T1sZzzrnC+M-gA@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=bauerman@br.ibm.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