Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Siddhesh Poyarekar <siddhesh@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] bitpos: Minor python changes for bitpos expansion
Date: Fri, 10 Aug 2012 20:42:00 -0000	[thread overview]
Message-ID: <87mx228ont.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20120811002716.61ba0e75@spoyarek> (Siddhesh Poyarekar's message	of "Sat, 11 Aug 2012 00:27:16 +0530")

>>>>> "Siddhesh" == Siddhesh Poyarekar <siddhesh@redhat.com> writes:

Siddhesh> Thanks, I've pushed the patch with the change you've asked for - sorry
Siddhesh> about it too, since you had told me about that function in an earlier
Siddhesh> change and I had managed to forget about it.

No worries.
In case it helps, I don't even remember that happening :-)

Tom


      reply	other threads:[~2012-08-10 20:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-04 19:24 Siddhesh Poyarekar
2012-08-10 16:59 ` Tom Tromey
2012-08-10 18:58   ` Siddhesh Poyarekar
2012-08-10 20:42     ` Tom Tromey [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=87mx228ont.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=siddhesh@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