From: Roland McGrath <roland@redhat.com>
To: overseers@sources.redhat.com
Cc: Ulrich Drepper <drepper@redhat.com>, Jakub Jelinek <jakub@redhat.com>
Subject: sources.redhat.com/pub/glibc
Date: Wed, 16 Jun 2004 06:27:00 -0000 [thread overview]
Message-ID: <200406152021.i5FKLe4b009790@magilla.sf.frob.com> (raw)
I would like for Jakub and I to be able to write the glibc ftp area on
sources, so that Uli doesn't need to hold hands for all future
bit-shovelling. Right now my roland@sources account can do only cvs server
AFAIK. We may also want to set up automated building of snapshot tarballs
and the like, along the lines of what gets done for gdb. I assume these
are all done as cron jobs and I should be able to do the same with my
account turned on fully.
Thanks,
Roland
reply other threads:[~2004-06-15 20:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200406152021.i5FKLe4b009790@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=overseers@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).