From: Ivo Raisr <ivosh@ivosh.net>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: overseers@sourceware.org
Subject: Re: Fwd: hosting Valgrind repository on sourceware.org
Date: Fri, 24 Feb 2017 16:08:00 -0000 [thread overview]
Message-ID: <CANXv6=vAr9wBOSaaJt5O9k2y1hnrZnAYrsbZqSHDPOdiATr3pA@mail.gmail.com> (raw)
In-Reply-To: <20170206210512.GJ41423@elastic.org>
2017-02-06 22:05 GMT+01:00 Frank Ch. Eigler <fche@elastic.org>:
>> Yes, please proceed.
>> What kind of credentials should I and the others provide?
>
> For each of you, visit <https://sourceware.org/cgi-bin/pdw/ps_form.cgi>
> project 'valgrind' of course, wherein you paste an ssh pubkey.
Thank you for setting up the Valgrind repo. We are currently in
migration beta testing.
Please could you make sure that from now on all the new account requests or
repo write access requests are approved with Julian Seward (jseward@acm.org).
He is the Valgrind architect and designer.
Right now there are up to 4 people with write access to Valgrind repository:
- Ivo Raisr (me)
- Julian Seward
- Mark Wielaard
- Philippe Waroquiers
Thank you,
I.
prev parent reply other threads:[~2017-02-24 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANXv6=u0Sp=Q=9=DPBEbniSKsmdNwZNLLvydnB7+7Y9321PZhw@mail.gmail.com>
[not found] ` <CANXv6=v5AkH=fvPQf1YDKyeqeCgzyDeVRmzuQDRb=XeFcnh-PA@mail.gmail.com>
[not found] ` <CANXv6=s75bVxUNSoP=Vqk7EXETArDDC5w3vtR+ZZBa2sWrAqig@mail.gmail.com>
[not found] ` <20170204225408.GF41423@elastic.org>
[not found] ` <CANXv6=vDYO7fbgygr9uHphMqQQFeCA3eNuaNdcg5GPZWyFPRTA@mail.gmail.com>
[not found] ` <20170206160126.GH41423@elastic.org>
[not found] ` <CANXv6=vx+2hZZzXq+BOHD6h0aq011isAjq0n7-yUZrxi4yDbfQ@mail.gmail.com>
2017-02-06 21:05 ` Frank Ch. Eigler
2017-02-09 22:37 ` Ivo Raisr
2017-02-09 22:44 ` Frank Ch. Eigler
2017-02-16 8:38 ` Ivo Raisr
2017-02-16 18:48 ` Frank Ch. Eigler
2017-02-16 19:30 ` Andrew Pinski
2017-02-24 16:08 ` Ivo Raisr [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='CANXv6=vAr9wBOSaaJt5O9k2y1hnrZnAYrsbZqSHDPOdiATr3pA@mail.gmail.com' \
--to=ivosh@ivosh.net \
--cc=fche@elastic.org \
--cc=overseers@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).