public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Chris Faylor <cgf@cygnus.com>
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: overseers@sourceware.cygnus.com
Subject: Re: cygwin-xfree
Date: Wed, 03 May 2000 19:53:00 -0000	[thread overview]
Message-ID: <20000503225326.A13697@cygnus.com> (raw)
Message-ID: <20000503195300.mjWG5USfEft8n55xg8LKtfxtS0X37jzzTI_WVOwu6sA@z> (raw)
In-Reply-To: <20000503194427.A27318@shell17.ba.best.com>

On Wed, May 03, 2000 at 07:44:27PM -0700, Jason Molenda wrote:
>> 2) I assume that if you all think that 1) is no problem then this directory
>>    should be winsup/xfree.  
>
>It almost seems like something you'd want to put in a separate
>repository.  I mean, it's _really_ Xfree86 with a few patches on
>top (OK, a lot of patches).  How would you handle e.g. make or perl
>(I'm trying to guess at programs that might have cygwin patches to
>them) if someone wanted to do the same?

Dunno.  I've been thinking that the winsup directory should be its
own little mini-build tree.  I didn't want to pollute the rest of
sourceware with stuff that was only intended for cygwin.

>> The winsup directory is not being mirrored by any of the CVS mirrors, right?
>
>If anyone is rsync'ing the entire src repository, they'll pick it
>up, but it's not the end of the world for them to end up with
>another ~150MB.  I would think about it more like "Where do I want
>third party programs that we maintain patches to be checked in?"
>
>Maybe a new repository, "cygwin-mods" or something, would be the cleanest
>approach.  But cygwin-mods is a terrible name.

Maybe cygwin-apps?

>If he ever does get ready to start importing Xfree86, please make sure
>he reads the CVS manual on tracking third party sources,
>	http://www.loria.fr/~molli/cvs/doc/cvs_13.html#SEC98
>
>or provide exact command lines for him.  It'd probably make sense
>to import the most recent release of xfree86, then the development
>version on which he's based his changes, and then check in his
>changes on top of that.

Yup.  I supplied the exact command lines for him.  And emphasized
repeatedly that he follow them exactly.  And he screwed them up...

>That way if he dies in a tragic pingpong ball manufacturing plant accident,
>people will be able to disentangle what he was up to.  It's really
>easy to import sources incorrectly, and annoying to recover from that
>at a later date.

I've repeatedly stressed this to him.  He spent all last night checking
everything in but somehow it never showed up on sourceware, or, at least
I can't find it.  He says that he understands why this happened.

>>I'm have mixed feelings about this.  If we can't provide this, the
>>developer will go to Source Forge.
>
>I don't have a strong opinion either, I did want to interject some
>facts about the system and stuff, tho.

Thanks, Jason.

cgf

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

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=20000503225326.A13697@cygnus.com \
    --to=cgf@cygnus.com \
    --cc=jason-swarelist@molenda.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).