Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Siva Chandra <sivachandra@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Fix a typo
Date: Fri, 08 Jun 2012 20:31:00 -0000	[thread overview]
Message-ID: <87ipf1czqf.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAGyQ6gyHCqm+jp=ahXOHHQLDF__WXTGEyj=A7Xu5ev8BbD1_+g@mail.gmail.com>	(Siva Chandra's message of "Sat, 9 Jun 2012 01:12:47 +0530")

>>>>> "Siva" == Siva Chandra <sivachandra@google.com> writes:

Siva> The attached patch fixes, what looks to me like, a definite typo.
Siva> 2012-06-08  Siva Chandra Reddy  <sivachandra@google.com>
Siva>         * valarith.c (binop_types_user_defined_p): Fix a typo.

This is ok.  Nice catch.

If it is possible to write a test case for this, that would be nice to
have.  But maybe it isn't possible without other fixes ... ?

Tom


  reply	other threads:[~2012-06-08 20:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08 19:43 Siva Chandra
2012-06-08 20:31 ` Tom Tromey [this message]
2012-06-09  7:38   ` Siva Chandra

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=87ipf1czqf.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sivachandra@google.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