Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Fernando Nasser <fnasser@cygnus.com>,
	GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: Re: Write after approval additions
Date: Wed, 14 Feb 2001 04:24:00 -0000	[thread overview]
Message-ID: <20010214072421.A3608@redhat.com> (raw)
In-Reply-To: <3A8986A4.783810A6@cygnus.com>

Hi -

cagney wrote:
: [...]
: Once someones name is in the MAINTAINERS file the people giving approval
: can be sure of the above all hold.  Significantly, they can be sure that
: the person has a valid assignment.
: 
: To turn the question around, how to BFD maintainers know if someone
: submitting a patch has a valid GDB assignment in place?

But that's a separate issue!  Vetting a patch based on whether
the contributor has a filed copyright assignment occurs before 
the patch is approved.  The MAINTAINERS file does not list all
people with assignments.


- FChE
-- 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE6inj1VZbdDOm/ZT0RAsgUAJ9bWl6ci5rT0PECgtikwm+EdCMeeACfR1t5
vClLhvypau8xkf9AiaKnf3I=
=9NzN
-----END PGP SIGNATURE-----
From cgf@redhat.com Wed Feb 14 06:53:00 2001
From: Christopher Faylor <cgf@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] sources.redhat.com -> sources.redhat.com
Date: Wed, 14 Feb 2001 06:53:00 -0000
Message-id: <20010214095356.I16327@redhat.com>
References: <200102132300.SAA17489@panix2.panix.com> <3A89C50B.48405663@cygnus.com>
X-SW-Source: 2001-02/msg00205.html
Content-length: 615

On Tue, Feb 13, 2001 at 06:36:43PM -0500, Andrew Cagney wrote:
>jkingdon@engr.sgi.com wrote:
>> 
>> At first I was going to call this an "obvious fix" as described in
>> MAINTAINERS, but in case I'm wrong, any objections?
>> 
>> 2001-02-13  Jim Kingdon  <jkingdon@engr.sgi.com>
>> 
>>         * CONTRIBUTE, README, TODO: sourceware.cygnus.com ->
>>         sources.redhat.com.  The nice thing about company names is that
>>         there are so many to choose from (don't get me started on logos :-)).
>
>I don't see any real point in the patch.  Why not just leave it until
>gdb.gnu.org is in place.

Ditto.

cgf


  reply	other threads:[~2001-02-14  4:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3A817ED7.60A7B32C@cygnus.com>
     [not found] ` <3A81AC7D.22AC2232@cygnus.com>
2001-02-09 10:06   ` Frank Ch. Eigler
2001-02-09 11:01     ` DJ Delorie
2001-02-09 12:35       ` Frank Ch. Eigler
2001-02-13 13:55     ` Andrew Cagney
2001-02-14  4:24       ` Frank Ch. Eigler [this message]
2001-02-14  7:50         ` Andrew Cagney
2001-02-14  7:54           ` 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=20010214072421.A3608@redhat.com \
    --to=fche@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=fnasser@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.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