From: Michael Chastain <mec.gnu@mindspring.com>
To: cagney@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Cleanup store.exp
Date: Tue, 27 Jul 2004 16:11:00 -0000 [thread overview]
Message-ID: <41067E95.nailF4S112QH6@mindspring.com> (raw)
In-Reply-To: <410678A8.8050401@gnu.org>
> Michael, look at the stats - you're reminding everyone.
Yes. Generally when I tell people that I want to know how they tested
their patches, they just come back and tell me how they tested the
patch. And I don't have to keep telling the same person, over and over.
With you, it's like tug-of-war, over and over.
Michael C
next prev parent reply other threads:[~2004-07-27 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 20:37 Michael Elizabeth Chastain
2004-07-26 20:56 ` Andrew Cagney
2004-07-27 0:44 ` Michael Chastain
2004-07-27 15:45 ` Andrew Cagney
2004-07-27 16:11 ` Michael Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-19 15:17 Andrew Cagney
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=41067E95.nailF4S112QH6@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.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