Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [rfa] Fix comment in can_use_hardware_watchpoint
Date: Fri, 02 Jul 2010 19:55:00 -0000	[thread overview]
Message-ID: <1278100516.5165.0.camel@hactar.cps.virtua.com.br> (raw)
In-Reply-To: <201007021321.o62DLUJ2022420@d12av02.megacenter.de.ibm.com>

On Fri, 2010-07-02 at 15:21 +0200, Ulrich Weigand wrote:
> Thiago Jung Bauermann wrote:
> 
> > 2010-07-01  Ulrich Weigand  <uweigand@de.ibm.com>
> > 	    Thiago Jung Bauermann  <bauerman@br.ibm.com>
> > 
> > 	* breakpoint.c (can_use_hardware_watchpoint): Answer "what does this
> > 	represent?" question in comment.  Change comment to a proper sentence.
> 
> This is OK, thanks.

Thanks, committed.


      reply	other threads:[~2010-07-02 19:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01 19:54 Thiago Jung Bauermann
2010-07-02 13:21 ` Ulrich Weigand
2010-07-02 19:55   ` Thiago Jung Bauermann [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=1278100516.5165.0.camel@hactar.cps.virtua.com.br \
    --to=bauerman@br.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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