public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Robert Buchholz <rbu@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Maciej Mrozowski <reavertm@poczta.fm>
Subject: Re: [gentoo-dev] Multimedia overlay
Date: Tue, 11 Aug 2009 14:57:43 +0200	[thread overview]
Message-ID: <200908111457.45249.rbu@gentoo.org> (raw)
In-Reply-To: <200908111240.35816.reavertm@poczta.fm>

[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]

On Tuesday 11 August 2009, Maciej Mrozowski wrote:
> On Tuesday 11 of August 2009 11:08:34 Robert Buchholz wrote:
> > In my opinion, the entrance barrier for devs is lower on
> > git.overlays, there is no signup, password, mail verification
> > required. There's scripts to keep the ssh keys in LDAP and on
> > git.overlays in sync, and people can just request access to at
> > overlays@g.o and usually get it done within 24 hours.
>
> Except usually it takes much longer than 24 hours (like over a month
> in my case).
> No, thank you.

Please do not generalise from your case. I do not have the history back 
when your key was added, but the last mail dates I could correlate to 
gitosis commits draw a different image:
2009-07-29: dev overlay creation, 80 minutes lag
2009-07-23: user key change, 27 minutes lag
2009-07-12: user added, 17 minutes lag
2009-06-09: user key change, 18:50 hours lag
2009-06-07: project overlay creation, 14:28 hours lag
2009-05-18: user key added, 14 minutes lag

If you need something, mail overlays@g.o and if no one replies within 
three days, mail again. And if you still encounter shortage of time, 
sign up to be a dev and help out.


Robert

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2009-08-11 12:57 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10 22:28 [gentoo-dev] Multimedia overlay Ben de Groot
2009-08-10 22:53 ` Sebastian Pipping
2009-08-10 23:22   ` Ben de Groot
2009-08-11  0:06 ` Thomas Sachau
2009-08-11  0:26   ` [gentoo-dev] " Nikos Chantziaras
2009-08-11  8:34   ` [gentoo-dev] " Markos Chandras
2009-08-11 22:21   ` Ben de Groot
2009-08-11  0:10 ` Mark Loeser
2009-08-11 22:26   ` Ben de Groot
2009-08-21  5:48     ` Mike Frysinger
2009-08-11  1:21 ` Federico Ferri
2009-08-11 13:31   ` Sebastian Pipping
2009-08-11  4:02 ` Josh Saddler
2009-08-11  4:40   ` Jeremy Olexa
2009-08-11  6:28     ` Josh Saddler
2009-08-11 13:34       ` Sebastian Pipping
2009-08-11 15:07         ` Arun Raghavan
2009-08-11 16:12           ` Maciej Mrozowski
2009-08-11 16:30             ` Nirbheek Chauhan
2009-08-11 17:22           ` Markos Chandras
2009-08-11 17:38             ` Arun Raghavan
2009-08-11 17:52               ` Nirbheek Chauhan
2009-08-11 17:56                 ` Arun Raghavan
2009-08-11 21:04                   ` Robin H. Johnson
2009-08-11 20:46               ` Maciej Mrozowski
2009-08-11 22:37               ` Ben de Groot
2009-08-12  1:38                 ` Arun Raghavan
2009-08-12 12:43                   ` Ben de Groot
2009-08-11  9:08   ` Robert Buchholz
2009-08-11 10:40     ` Maciej Mrozowski
2009-08-11 12:57       ` Robert Buchholz [this message]
2009-09-03 18:42 ` [gentoo-dev] " Nikos Chantziaras
2009-09-03 18:47   ` Jeremy Olexa

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=200908111457.45249.rbu@gentoo.org \
    --to=rbu@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=reavertm@poczta.fm \
    /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