Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Siva Chandra <sivachandra@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [Patch] PR python/15464 and python/16113
Date: Tue, 14 Jan 2014 14:48:00 -0000	[thread overview]
Message-ID: <CAGyQ6gwhR+XV2Hpm4JGBQam3gsP6im4v7i0EcV3Mc0KqnDK8kQ@mail.gmail.com> (raw)
In-Reply-To: <87ppnvziuw.fsf@fleche.redhat.com>

On Mon, Jan 13, 2014 at 1:12 PM, Tom Tromey <tromey@redhat.com> wrote:
> This patch is ok with those two nits fixed.

Forgot to ask, should this go into 7.7 branch as well? The first patch
is in 7.7.

Thanks,
Siva Chandra


  parent reply	other threads:[~2014-01-14 14:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-27 22:38 Siva Chandra
2013-12-30 14:27 ` Siva Chandra
2014-01-06 20:50   ` Tom Tromey
2014-01-07 14:28     ` Siva Chandra
2014-01-13 21:12       ` Tom Tromey
2014-01-14  1:51         ` Siva Chandra
2014-01-14 14:48         ` Siva Chandra [this message]
2014-01-14 14:50           ` Tom Tromey
2014-01-15 12:46             ` Joel Brobecker
2014-01-15 13:19               ` Siva Chandra
2014-01-06 20:36 ` Tom Tromey

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=CAGyQ6gwhR+XV2Hpm4JGBQam3gsP6im4v7i0EcV3Mc0KqnDK8kQ@mail.gmail.com \
    --to=sivachandra@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.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