From: "Frank Ch. Eigler" <fche@redhat.com>
To: Kevin Anderson <kanderso@redhat.com>
Cc: cluster-list@redhat.com, overseers@sources.redhat.com
Subject: Re: New Projects for sources.redhat.com
Date: Wed, 19 May 2004 19:29:00 -0000 [thread overview]
Message-ID: <20040519183913.GE25826@redhat.com> (raw)
In-Reply-To: <1084991290.3982.118.camel@dhcp64-191.boston.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 661 bytes --]
Hi -
> At the moment, we have multiple independent cvs trees for the different
> elements. Can we have multiple cvs trees under a single sourceware
> project?
I'm not aware of existing sourceware projects that use multiple CVSROOTs.
This is perhaps because of the degree of interlinking between CVS and the
rest of the system (email patch distribution, archiving, possible bugzilla,
etc.), or general system overhead.
In general, we'd prefer not to fragment sourceware into too many tiny
projects unless absolutely necessary. For example, what sort of
administrative structure (group membership) differences do you forsee
between the subprojects?
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-19 18:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 16:53 Kevin Anderson
2004-05-19 18:28 ` Frank Ch. Eigler
2004-05-19 18:39 ` Kevin Anderson
2004-05-19 19:29 ` Frank Ch. Eigler [this message]
2004-05-20 11:55 ` David Teigland
2004-05-20 13:44 ` Alasdair G Kergon
2004-05-20 14:32 ` Lon Hohberger
2004-05-20 17:11 ` Christopher Faylor
2004-05-25 18:23 ` Frank Ch. Eigler
2004-05-25 18:47 ` Brian Stevens
2004-05-25 19:15 ` Alasdair G Kergon
[not found] ` <20040525174912.GS19299@agk.surrey.redhat.com>
2004-05-25 19:07 ` Frank Ch. Eigler
2004-05-20 1:55 ` Gerald Pfeifer
2004-06-22 13:28 Alasdair G Kergon
2004-06-24 16:37 ` Frank Ch. Eigler
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=20040519183913.GE25826@redhat.com \
--to=fche@redhat.com \
--cc=cluster-list@redhat.com \
--cc=kanderso@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).