public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: overseers@sources.redhat.com
Subject: creating glibc-ports CVS repository?
Date: Sat, 17 Jul 2004 05:53:00 -0000	[thread overview]
Message-ID: <or4qo718nx.fsf@livre.redhat.lsd.ic.unicamp.br> (raw)

glibc has recently been added some infrastructure to support drop-in
add-on ports.  The first such port I'm aware of is the am33/2.0 port.
I suspect the mips port may soon be required to move out of glibc,
since it doesn't even build.  I'd like to soon contribute an frv port
as well.

I was thinking we might be able to maintain them in the glibc CVS
repository, but, erhm, some recent developments made me think this
isn't going to work :-)

So I'm thinking it would be nice to create a separate CVS repository,
perhaps with its own mailing list and, perhaps, a home page.  Could we
have this set up?  I volunteer to be the project maintainer for the
time being.  I hope other maintainers of ports that can't make it to
the main glibc tree, or that get pushed out of that tree, join this
project and maintain their ports in this separate repository.

What's the procedure to get such a new project added to s.r.c?

Thanks,

-- 
Alexandre Oliva             http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}

             reply	other threads:[~2004-07-17  5:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-17  5:53 Alexandre Oliva [this message]
2004-07-17 14:28 ` Ian Lance Taylor
2004-07-17 22:25   ` Alexandre Oliva

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=or4qo718nx.fsf@livre.redhat.lsd.ic.unicamp.br \
    --to=aoliva@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).