From: Manoj Iyer <manjo@austin.ibm.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: New thread testcase (resubmit)
Date: Fri, 27 Aug 2004 19:54:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0408271419160.19165@lazy> (raw)
In-Reply-To: <412F8F66.1070503@redhat.com>
> Manoj Iyer wrote:
> > Michael,
> >
> > Incorporated your comments.
>
> Ok, thanks, this is good.
> Are you write-after-approval yet?
>
ie am I approved from FSF? yes according to the conversation I had with my
management I understand I am.
next prev parent reply other threads:[~2004-08-27 19:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 16:32 Manoj Iyer
2004-08-27 17:55 ` Michael Snyder
2004-08-27 18:51 ` Manoj Iyer
2004-08-27 19:45 ` Michael Snyder
2004-08-27 19:54 ` Manoj Iyer [this message]
2004-08-30 23:20 ` Manoj Iyer
2004-08-31 21:41 ` New thread testcase (ok to commit??) Manoj Iyer
2004-08-31 20:02 ` [COMMIT] New thread testcase Manoj Iyer
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=Pine.LNX.4.58.0408271419160.19165@lazy \
--to=manjo@austin.ibm.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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