Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Kei Sakamoto" <sakamoto.kei@renesas.com>
To: "Andrew Cagney" <ac131313@redhat.com>
Cc: <gdb-patches@sources.redhat.com>
Subject: Re: [PATCH] multi-arching m32r
Date: Tue, 08 Jul 2003 05:14:00 -0000	[thread overview]
Message-ID: <01b601c34510$26558d00$5169910a@KEI> (raw)
In-Reply-To: <002901c341c0$f64fff70$5169910a@KEI>

> Andrew,
> 
> > 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.
> 
> Thank you for recommending me for the write after approval list.
> But I found that I could not use my account, because SSH access
> is prohibited by our company's network policy.
> 
> I'm negotiating with our network administrator about it now.
> I'll add myself to gdb/MAINTAINERS after I get the permission.

Our network administrator rejected my request. He said that 
any other ports excepts http port and ftp port were prohibited
because of the security reason. It seems that I'll never be able
to use SSH and CVS access...

Would you commit patches I posted if they are OK?

===
Kei Sakamoto
Renesas Technology Corp.
sakamoto.kei@renesas.com


  reply	other threads:[~2003-07-08  5:14 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
2003-07-04  0:10             ` Kei Sakamoto
2003-07-08  5:14               ` Kei Sakamoto [this message]
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='01b601c34510$26558d00$5169910a@KEI' \
    --to=sakamoto.kei@renesas.com \
    --cc=ac131313@redhat.com \
    --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