Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: overseers@sourceware.org, Ulrich Weigand <uweigand@de.ibm.com>,
		gdb-patches@sourceware.org, Daniel Jacobowitz <drow@false.org>
Subject: Re: ARI no longer updated?
Date: Fri, 22 Jun 2007 15:12:00 -0000	[thread overview]
Message-ID: <20070622151252.GA16662@ednor> (raw)
In-Reply-To: <20070622135626.GA12381@caradoc.them.org>

On Fri, Jun 22, 2007 at 09:56:26AM -0400, Daniel Jacobowitz wrote:
>Overseers, could someone at least make ~gdbadmin a+x (it's already
>a+r)?  Maybe someone else should have access to this account now...

I added Daniel to the gdbadmin group and added his ssh public key to
.ssh/authorized_keys.  Joel Broebecker should have already had login
rights to the gdbadmin account but I added his username to the gdbadmin
group as well.

FYI

cgf


      reply	other threads:[~2007-06-22 15:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-22 13:42 Ulrich Weigand
2007-06-22 13:56 ` Daniel Jacobowitz
2007-06-22 15:12   ` Christopher Faylor [this message]

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=20070622151252.GA16662@ednor \
    --to=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=overseers@sourceware.org \
    --cc=uweigand@de.ibm.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