public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: richard.j.ward1@googlemail.com
Cc: Project Archer <archer@sourceware.org>
Subject: Re: [python][patch] Info about base class in gdb.Type
Date: Thu, 03 Dec 2009 21:23:00 -0000	[thread overview]
Message-ID: <4B182C3C.6020109@redhat.com> (raw)
In-Reply-To: <1257191415.21520.6.camel@elemental-lin>

>> On 11/02/2009 01:59 PM, Phil Muldoon wrote:
>> Oops part of my patch fixes a buglet in your is_base_class patch; the 
>> other section adds the beginnings of a testsuite for Python types.  I 
>> can just merge the patches, ChangeLogs and submit it all upstream as one 
>> patch. What do you think?
>
> On 11/02/2009 07:50 PM, Richard Ward wrote:
>
> Sounds fine to me.
> 
> The only thing is I was rather hoping that my email would appear in
> either the ChangeLogs or the version control logs (I'm looking for work
> at the moment, and if I say in my CV or an interview that I submitted
> some small patches to gdb I'd like to be able to prove it). Will that be
> the case? If not then its not the end of the world.

I went ahead and committed this today to FSF upstream:

http://sourceware.org/ml/gdb-cvs/2009-12/msg00018.html

Cheers,

Phil

  parent reply	other threads:[~2009-12-03 21:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18 13:50 Richard Ward
2009-11-02 13:59 ` Phil Muldoon
2009-11-02 15:10   ` Phil Muldoon
2009-11-02 19:50     ` Richard Ward
2009-11-02 20:42       ` Phil Muldoon
2009-12-03 21:23       ` Phil Muldoon [this message]
2009-12-04  3:53         ` Richard Ward

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=4B182C3C.6020109@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=archer@sourceware.org \
    --cc=richard.j.ward1@googlemail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).