From: justin <jlec@gentoo.org>
To: gentoo-science@lists.gentoo.org
Subject: [gentoo-science] Github commit access broken
Date: Mon, 10 Dec 2012 15:23:11 +0100 [thread overview]
Message-ID: <50C5F04F.9090201@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 230 bytes --]
Hi,
I accidentally broken the commit access for many contributors on github.
I am trying to revert this, but in worst case we need to activate it
again for everyone who had direct access.
I am sorry for that,
Justin
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]
next reply other threads:[~2012-12-10 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 14:23 justin [this message]
2012-12-10 18:45 ` [gentoo-science] Github commit access broken Justin
2012-12-11 8:09 ` justin
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=50C5F04F.9090201@gentoo.org \
--to=jlec@gentoo.org \
--cc=gentoo-science@lists.gentoo.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