From: Andrew Cagney <ac131313@redhat.com>
To: Doug Evans <dje@sebabeach.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] update cgen read_memory_func
Date: Wed, 18 Jun 2003 16:29:00 -0000 [thread overview]
Message-ID: <3EF0935C.7040500@redhat.com> (raw)
In-Reply-To: <20030618155926.46273B536@mail.sebabeach.org>
> I'm not sure what you're saying.
> Are you saying someone else needs to check this in?
> Or are you saying that this patch can't go in at all?
>
> This patch doesn't need a copyright assignment. It's far too small.
> [Otherwise I wouldn't have gone to this trouble...]
From gdb/MAINTAINERS:
> Write After Approval
> (alphabetic)
>
> To get recommended for the Write After Approval list you need a valid
> FSF assignment and have submitted one good patch.
Please do not assume that your ability to make changes in the SRC
repository gives you permission to make changes to it.
Send the patch to gdb-patches and I'm sure someone will check it in.
Andrew
next prev parent reply other threads:[~2003-06-18 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 5:33 Doug Evans
2003-06-18 15:03 ` Andrew Cagney
2003-06-18 16:08 ` Doug Evans
2003-06-18 16:29 ` Andrew Cagney [this message]
2003-06-18 16:51 ` Doug Evans
2003-06-20 17:38 ` Frank Ch. Eigler
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=3EF0935C.7040500@redhat.com \
--to=ac131313@redhat.com \
--cc=dje@sebabeach.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