From: Andrew Cagney <ac131313@cygnus.com>
To: Jason Merrill <jason@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH to testsuite/gdb.c++/userdef.cc
Date: Tue, 08 Jan 2002 16:34:00 -0000 [thread overview]
Message-ID: <3C3B9000.4090209@cygnus.com> (raw)
In-Reply-To: <wvlsn9glf65.fsf@prospero.cambridge.redhat.com>
> "Andrew" == Andrew Cagney <ac131313@cygnus.com> writes:
>
>
>>> I've gone ahead and checked this in; hope that's OK.
>
>
>> Not really.
>
>
> Sorry, I figured it would fall under the obvious fix rule. But...
It would, if you were in the MAINTAINERS file.
In case you're wondering, getting write-after-approval access is pretty
easy. Just:
o submit a single good patch
(suggest a one line indentation fix
or even something removing a ``register''
attribute from a declaration)
o have an assignment
enjoy,
Andrew
next prev parent reply other threads:[~2002-01-09 0:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 8:03 Jason Merrill
2002-01-08 12:29 ` Andrew Cagney
2002-01-08 13:13 ` Jason Merrill
2002-01-08 16:34 ` Andrew Cagney [this message]
2002-01-08 8:40 Michael Elizabeth Chastain
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=3C3B9000.4090209@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jason@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