Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Cleanup store.exp
Date: Tue, 27 Jul 2004 15:45:00 -0000	[thread overview]
Message-ID: <410678A8.8050401@gnu.org> (raw)
In-Reply-To: <4105A468.nailMK71QB5ZQ@mindspring.com>


> I hate to put it like this, but I can't find a better way:
> you're the only person I'm having trouble getting to comply.

Michael, look at the stats - you're reminding everyone.  It's just that 
I'm submitting far more patches than anyone else and, not unsuprisingly, 
am being reminded more often.  This is after all a very new and very 
foreign requirement and one that will take time to get accustomed to.

Please show just a little tollerance of your peers.

shesh,
Andrew



  reply	other threads:[~2004-07-27 15:45 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 [this message]
2004-07-27 16:11       ` Michael Chastain
  -- 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=410678A8.8050401@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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