From: Ian Lance Taylor <ian@airs.com>
To: Fernando Nasser <fnasser@redhat.com>
Cc: overseers@sources.redhat.com
Subject: Re: Yum repository [Was: Yam repository]
Date: Thu, 04 Dec 2003 17:46:00 -0000 [thread overview]
Message-ID: <m3oeuo4gst.fsf@gossamer.airs.com> (raw)
In-Reply-To: <3FCF6938.6050001@redhat.com>
Fernando Nasser <fnasser@redhat.com> writes:
> And there is the matter of policy. Are sources.redhat.com projects to
> be allowed to set up Yum repositories for themselves? (I don't know
> how much extra traffic it will generate -- maybe it will be just more
> convenient than ftp but the bandwidth will be about the same).
I don't think we really have policy on sourceware. Just a bunch of
people who do random stuff, and Red Hat who supports us.
I suppose we could start doing policy, though. Any idea where can we
download it from?
Ian
next prev parent reply other threads:[~2003-12-04 17:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 15:12 Yam repository Fernando Nasser
2003-12-04 15:27 ` Frank Ch. Eigler
2003-12-04 17:04 ` Yum repository [Was: Yam repository] Fernando Nasser
2003-12-04 17:46 ` Ian Lance Taylor [this message]
2003-12-04 17:58 ` Matthew Galgoci
2003-12-04 18:12 ` Christopher Faylor
2003-12-04 18:47 ` Fernando Nasser
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=m3oeuo4gst.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=fnasser@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).