From: Roland McGrath <roland@hack.frob.com>
To: overseers@sourceware.org
Subject: glibc-buildbot.git
Date: Tue, 25 Aug 2015 23:39:00 -0000 [thread overview]
Message-ID: <20150825233929.363F72C3A92@topped-with-meat.com> (raw)
I've created a new git repository in:
/sourceware/projects/glibc-home/gitfiles-buildbot/
I don't have appropriate permissions to add a symlink to it from
/sourceware/git/glibc-buildbot.git (I'm not in the sourceware group).
Is there anything other than making that symlink that's necessary for
a new repository to be accessible via git, ssh, and gitweb?
I'd be happy to get more privileges on sourceware so as to be able to do
these adminy things myself if that's easier. Or else please make that
symlink and whatever else is required.
Thanks,
Roland
next reply other threads:[~2015-08-25 23:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 23:39 Roland McGrath [this message]
2015-08-26 0:56 ` glibc-buildbot.git Frank Ch. Eigler
2015-08-26 16:54 ` glibc-buildbot.git Roland McGrath
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=20150825233929.363F72C3A92@topped-with-meat.com \
--to=roland@hack.frob.com \
--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).