public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Chris Faylor <cgf@cygnus.com>
To: Marc van Woerkom <van.woerkom@netcologne.de>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: ANN: das blinkenlights 0.0.1 cygwin distro
Date: Sat, 04 Dec 1999 13:24:00 -0000	[thread overview]
Message-ID: <19991204162353.B1386@cygnus.com> (raw)
In-Reply-To: <199912041830.TAA02960@oranje.my.domain>

On Sat, Dec 04, 1999 at 07:30:02PM +0100, Marc van Woerkom wrote:
>Originally I had a bit of time left and just wanted to check the source tree
>if a certain patch that I have in mind for some time now had been realized 
>by someone else in the meantime.
>
>Turned out that this is not as easy as I thought. 

How is downloading the winsup/newlib sources difficult?

>> There are few reasons why this hasn't happened so far: 
>> 1) We're lacking resources for this,
>
>Can't believe that one. 
>
>Are you telling me you handle this project without some sort of 
>configuration management on your disks? Just patch sets? 

We're talking about external repositories, aren't we?  Of course we have
an internal repository.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

WARNING: multiple messages have this Message-ID
From: Chris Faylor <cgf@cygnus.com>
To: Marc van Woerkom <van.woerkom@netcologne.de>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: ANN: das blinkenlights 0.0.1 cygwin distro
Date: Fri, 31 Dec 1999 13:28:00 -0000	[thread overview]
Message-ID: <19991204162353.B1386@cygnus.com> (raw)
Message-ID: <19991231132800.ks7FRTg3nbx7rdH07e08F_clZDhCg1PYoLqyPuoadKY@z> (raw)
In-Reply-To: <199912041830.TAA02960@oranje.my.domain>

On Sat, Dec 04, 1999 at 07:30:02PM +0100, Marc van Woerkom wrote:
>Originally I had a bit of time left and just wanted to check the source tree
>if a certain patch that I have in mind for some time now had been realized 
>by someone else in the meantime.
>
>Turned out that this is not as easy as I thought. 

How is downloading the winsup/newlib sources difficult?

>> There are few reasons why this hasn't happened so far: 
>> 1) We're lacking resources for this,
>
>Can't believe that one. 
>
>Are you telling me you handle this project without some sort of 
>configuration management on your disks? Just patch sets? 

We're talking about external repositories, aren't we?  Of course we have
an internal repository.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~1999-12-04 13:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-02 14:18 Marc van Woerkom
1999-12-02 18:26 ` Christopher Faylor
1999-12-04 11:52   ` Marc van Woerkom
1999-12-04 13:24     ` Chris Faylor [this message]
1999-12-04 16:44       ` Marc van Woerkom
1999-12-04 16:56         ` Chris Faylor
1999-12-04 17:44           ` Marc van Woerkom
1999-12-31 13:28             ` Marc van Woerkom
1999-12-31 13:28           ` Chris Faylor
1999-12-31 13:28         ` Marc van Woerkom
1999-12-31 13:28       ` Chris Faylor
1999-12-31 13:28     ` Marc van Woerkom
1999-12-31 13:28   ` Christopher Faylor
1999-12-31 13:28 ` Marc van Woerkom
  -- strict thread matches above, loose matches on Subject: below --
1999-12-02 16:48 varun sharma
1999-12-31 13:28 ` varun sharma
1999-11-24 16:29 varun sharma
1999-11-30 23:39 ` varun sharma

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=19991204162353.B1386@cygnus.com \
    --to=cgf@cygnus.com \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=van.woerkom@netcologne.de \
    /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).