public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Chris Faylor <cgf@cygnus.com>
Cc: overseers@sourceware.cygnus.com
Subject: Re: cygwin-xfree
Date: Wed, 03 May 2000 19:30:00 -0000	[thread overview]
Message-ID: <3910E06F.45BA721B@cygnus.com> (raw)
Message-ID: <20000503193000.zdco1tLOpXQzodwBPH6A6FejIMN9mb_1Th1GnyPWLoU@z> (raw)
In-Reply-To: <20000503221805.A13179@cygnus.com>

Chris Faylor wrote:
> 
> I have recently offered CVS space to the the guy who has been working on
> the port of XFree86 to Cygwin.
> 
> I thought he wanted it to upload the source code for a few drivers.
> 
> It turns out that he wants to upload pretty much all of the XFree86
> source code since there were, apparently, a number of changes required
> for Cygwin.
> 
> So, two question:
> 
> 1) What does everyone think about adding another 150MB to the server.  There
>    seems to be more than adequate disk space available for this but 150MB
>    is still a pretty massive project.  I can just imagine what will happen
>    to sourceware the first time someone checks this out.
> 
> 2) I assume that if you all think that 1) is no problem then this directory
>    should be winsup/xfree.  The winsup directory is not being mirrored by
>    any of the CVS mirrors, right?
> 
> I'm have mixed feelings about this.  If we can't provide this, the developer
> will go to Source Forge.  Maybe that's the best thing.  He's already split
> the development that had started for cygwin so that there is just a generic
> msvc/mingw version of everything as well as a cygwin-specific branch.  It
> would probably be not too much work to set up on Source Forge and maybe
> it would even give Cygwin a little publicity.

Where is the public xfree86 CVS repository? Hmm:

http://www.xfree86.org/developer.html
> To become an XFree86 developer you first need to join The XFree86
> Project as a non-voting member. Access to the XFree86 development
> code is only available to project members, and being a member provides
> the necessary legal status to allow developers to access information
> available to the project from other sources. 

there isn't one.

	Andrew

  parent reply	other threads:[~2000-05-03 19:30 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 Jeffrey A Law
2000-05-04  9:07   ` cygwin-xfree Jeffrey A Law
2000-12-30  6:08 ` Andrew Cagney [this message]
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 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       ` 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           ` cygwin-xfree Chris Faylor
2000-05-04  7:48             ` cygwin-xfree Chris Faylor
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 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 Jason Molenda
2000-05-03 19:45   ` cygwin-xfree Jason Molenda
2000-12-30  6:08   ` cygwin-xfree Chris Faylor
2000-05-03 19:53     ` cygwin-xfree Chris Faylor
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

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=3910E06F.45BA721B@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=cgf@cygnus.com \
    --cc=overseers@sourceware.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).