Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Gilliam <pgilliam@us.ibm.com>
To: gdb-patches@sources.redhat.com
Cc: Michael Elizabeth Chastain <mec.gnu@mindspring.com>,
	Andrew Cagney <cagney@gnu.org>
Subject: Re: Avoid timeouts in call-sc.exp
Date: Tue, 31 Aug 2004 20:48:00 -0000	[thread overview]
Message-ID: <200408311346.36102.pgilliam@us.ibm.com> (raw)
In-Reply-To: <200408311228.41096.pgilliam@us.ibm.com>

On Tuesday 31 August 2004 12:28, Paul Gilliam wrote:
> On Thursday 26 August 2004 14:41, Andrew Cagney wrote:
> > (I see michael got a bit ahead of himself.)
> >
> > Paul,
> >
> > Can you please:
> >
> > - create a new patch to MAINTAINERS adding your self to write after
> > approval (its alphabetic)
> >
> > - add a corresponding ChangeLog
> >
> > - post both to gdb-patches
> >
> > - commit just this change.
> >
> > This, if nothing else confirms that you can use CVS.
> >
> > Once that's done you can go back to Michael's patch.
> >
> > Andrew
>
> Andrew,
> Here is the patch...  I will commit this in 1 hour unless I hear from
> someone.
>
>
> 004-08-31  Paul Gilliam  <pgilliam@us.ibm.com>
>
>         * MAINTAINERS: Add self to Write-After-Approval.
>
>
> diff -c -3 -p -r1.286 MAINTAINERS
> *** MAINTAINERS 30 Aug 2004 20:05:41 -0000      1.286
> --- MAINTAINERS 31 Aug 2004 19:26:17 -0000
> *************** Adam Fedor                                     
> fedor@gnu.org *** 340,345 ****
> --- 340,346 ----
>   Fred Fish                                     fnf@ninemoons.com
>   Brian Ford                                    ford@vss.fsi.com
>   Orjan Friberg                                 orjanf@axis.com
> + Paul Gilliam                                  pgilliam@us.ibm.com
>   Raoul Gough                                   RaoulGough@yahoo.co.uk
>   Anthony Green                                 green@redhat.com
>   Matthew Green                                 mrg@eterna.com.au

committed
-=# Paul #=-


      reply	other threads:[~2004-08-31 20:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18 21:28 Paul Gilliam
2004-08-18 21:58 ` Michael Chastain
2004-08-20 10:34 ` Michael Chastain
2004-08-20 16:17   ` Paul Gilliam
2004-08-23 21:11   ` Paul Gilliam
2004-08-23 21:55     ` Michael Chastain
2004-08-24 16:15       ` Paul Gilliam
2004-08-24 17:26         ` Michael Chastain
2004-08-24 18:50           ` Paul Gilliam
2004-08-24 18:52             ` Daniel Jacobowitz
2004-08-24 18:55             ` Michael Chastain
2004-08-24 19:14               ` Paul Gilliam
2004-08-25 17:54       ` Paul Gilliam
2004-08-25 18:11         ` Michael Chastain
2004-08-25 18:21           ` Paul Gilliam
2004-08-25 18:52             ` Michael Chastain
2004-08-25 19:08           ` Paul Gilliam
2004-08-26 14:17             ` Michael Chastain
2004-08-26 16:17               ` Paul Gilliam
2004-08-26 16:26                 ` Michael Chastain
2004-08-26 16:34                   ` Paul Gilliam
     [not found] ` <200408261227.58890.pgilliam@us.ibm.com>
     [not found]   ` <412E5915.8010401@gnu.org>
2004-08-31 19:30     ` Paul Gilliam
2004-08-31 20:48       ` Paul Gilliam [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=200408311346.36102.pgilliam@us.ibm.com \
    --to=pgilliam@us.ibm.com \
    --cc=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