From: Tom Tromey <tromey@redhat.com>
To: Sami Wagiaalla <swagiaal@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/2] namespace support
Date: Fri, 19 Jun 2009 21:44:00 -0000 [thread overview]
Message-ID: <m3y6rnrja7.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m33a9vsybo.fsf@fleche.redhat.com> (Tom Tromey's message of "Fri\, 19 Jun 2009 15\:33\:47 -0600")
>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
Tom> The version of this patch with the new test case is ok.
Tom> Thanks.
I saw you didn't have write access, so I set you up with
write-after-approval access.
Tom
prev parent reply other threads:[~2009-06-19 21:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 14:48 Sami Wagiaalla
2009-06-02 15:13 ` Sami Wagiaalla
2009-06-05 0:27 ` Tom Tromey
2009-06-19 19:43 ` Sami Wagiaalla
2009-06-19 20:15 ` Sami Wagiaalla
2009-06-19 21:33 ` Tom Tromey
2009-06-19 21:44 ` 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=m3y6rnrja7.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=swagiaal@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