From: Chris Faylor <cgf@cygnus.com>
To: Jim Kingdon <kingdon@redhat.com>
Cc: tromey@cygnus.com, overseers@sourceware.cygnus.com
Subject: Re: cygwin-xfree
Date: Thu, 04 May 2000 07:48:00 -0000 [thread overview]
Message-ID: <20000504104843.A14875@cygnus.com> (raw)
Message-ID: <20000504074800.mK00CGz2OHQklQPEQipJaJ2IvbvO08BwtLOh8e9f8zE@z> (raw)
In-Reply-To: <200005041152.HAA17664@devserv.devel.redhat.com>
On Thu, May 04, 2000 at 07:52:02AM -0400, Jim Kingdon wrote:
>As for cygwin-xfree, I'm still looking for objections to suggesting
>they go to sourceforge. One of the requirements for being on
>kingdon-rules.redhat.com, er, sourceware.cygnus.com, is a sponsor
>within Red Hat and in the XFree case we only seem to have one partial
>reluctant one (Chris). It's different than Cygwin itself as nearly as
>I can tell.
I didn't mean to portray reluctance. I *am* really interested in having
this on sourceware. I just wanted to make sure that everyone realized
that I was not going to stomp my feet if the consensus was that
sourceware should not host this. I probably went a little too much
in the other direction when I mentioned Source Forge.
cgf
next prev parent reply other threads:[~2000-05-04 7:48 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 cygwin-xfree Chris Faylor
2000-05-03 19:18 ` cygwin-xfree Chris Faylor
2000-12-30 6:08 ` cygwin-xfree Tom Tromey
2000-05-03 19:59 ` cygwin-xfree Tom Tromey
2000-12-30 6:08 ` cygwin-xfree Chris Faylor
2000-05-03 20:07 ` cygwin-xfree Chris Faylor
2000-12-30 6:08 ` cygwin-xfree Tom Tromey
2000-05-03 20:09 ` cygwin-xfree Tom Tromey
2000-12-30 6:08 ` libstdc++-v3 things that still are not working correctly Benjamin Kosnik
2000-05-03 20:14 ` Benjamin Kosnik
2000-12-30 6:08 ` Jeffrey A Law
2000-05-03 22:33 ` Jeffrey A Law
2000-12-30 6:08 ` cygwin-xfree Chris Faylor
2000-05-03 20:22 ` cygwin-xfree Chris Faylor
2000-12-30 6:08 ` cygwin-xfree Bob Manson
2000-05-03 21:11 ` cygwin-xfree Bob Manson
2000-12-30 6:08 ` cygwin-xfree Jason Molenda
2000-05-04 13:19 ` cygwin-xfree Jason Molenda
2000-12-30 6:08 ` cygwin-xfree Jim Kingdon
2000-05-07 6:32 ` cygwin-xfree Jim Kingdon
2000-12-30 6:08 ` cygwin-xfree Stan Shebs
2000-05-21 22:19 ` cygwin-xfree Stan Shebs
2000-12-30 6:08 ` cygwin-xfree Mark Galassi
2000-05-22 6:15 ` cygwin-xfree Mark Galassi
2000-12-30 6:08 ` cygwin-xfree Jim Kingdon
2000-05-04 4:52 ` cygwin-xfree Jim Kingdon
2000-12-30 6:08 ` Chris Faylor [this message]
2000-05-04 7:48 ` cygwin-xfree Chris Faylor
2000-12-30 6:08 ` cygwin-xfree Per Bothner
2000-05-03 23:21 ` cygwin-xfree Per Bothner
2000-12-30 6:08 ` cygwin-xfree Jim Kingdon
2000-05-04 4:35 ` cygwin-xfree Jim Kingdon
2000-12-30 6:08 ` cygwin-xfree Andrew Cagney
2000-05-03 19:30 ` cygwin-xfree Andrew Cagney
2000-12-30 6:08 ` cygwin-xfree Chris Faylor
2000-05-03 19:34 ` cygwin-xfree Chris Faylor
2000-12-30 6:08 ` cygwin-xfree Jim Kingdon
2000-05-03 19:47 ` cygwin-xfree Jim Kingdon
2000-12-30 6:08 ` cygwin-xfree Jeffrey A Law
2000-05-04 9:07 ` cygwin-xfree Jeffrey A Law
2000-12-30 6:08 ` cygwin-xfree Jason Molenda
2000-05-03 19:45 ` cygwin-xfree Jason Molenda
2000-12-30 6:08 ` htdig, was cygwin-xfree Frank Ch. Eigler
2000-05-03 20:23 ` Frank Ch. Eigler
2000-12-30 6:08 ` Hans-Peter Nilsson
2000-05-06 2:43 ` Hans-Peter Nilsson
2000-12-30 6:08 ` cygwin-xfree Chris Faylor
2000-05-03 19:53 ` cygwin-xfree Chris Faylor
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=20000504104843.A14875@cygnus.com \
--to=cgf@cygnus.com \
--cc=kingdon@redhat.com \
--cc=overseers@sourceware.cygnus.com \
--cc=tromey@cygnus.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).