Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Kei Sakamoto <sakamoto.kei@renesas.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] multi-arching m32r
Date: Wed, 02 Jul 2003 01:09:00 -0000	[thread overview]
Message-ID: <3F0230AD.2070205@redhat.com> (raw)
In-Reply-To: <3EEF2676.1080308@redhat.com>

> Can I post new m32r files with deprecated functions and
> 
>>> > take care of their deprecated code later?
> 
>> 
> 
>>> 
>>> Once the assignment is in place, they can certainly be posted.
>>> Unfortunatly, they won't be accepted for the mainline until they pass
>>> the `new architecture' acceptance criteria.
> 
> 
> Unfortunatly, there is no assignment in place.  Once the assignment is
> in place (you and your employeer have received the paperwork back)
> please re-post this.  At that point someone will pick it up.

The assignment's arrived.  Kei, once your account is created can you
please add yourself to gdb/MAINTAINERS write after approval list.  Don't
forget to include a ChangeLog entry and post the patch.

Look forward to the revised m32r patches.

Andrew



  reply	other threads:[~2003-07-02  1:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-09  9:52 Kei Sakamoto
2003-05-09 20:36 ` Andrew Cagney
2003-06-16 10:33   ` Kei Sakamoto
2003-06-16 12:49     ` Andrew Cagney
2003-06-17 10:02       ` Kei Sakamoto
2003-06-17 14:32         ` Andrew Cagney
2003-07-02  1:09           ` Andrew Cagney [this message]
2003-07-04  0:10             ` Kei Sakamoto
2003-07-08  5:14               ` Kei Sakamoto
2003-07-08  6:10                 ` Joel Brobecker
2003-07-08  6:18                   ` Kei Sakamoto
2003-08-07  5:12               ` [commit] addition to gdb/MAINTAINERS Kei Sakamoto

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=3F0230AD.2070205@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=sakamoto.kei@renesas.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