Re: Speaking of debian cygwin

2001-12-06 Thread Keith Starsmeare
Would it be rude of me to request the people refrain from cross-posting to the cygwin mailing lists? We seem to be getting quite a lot of news from other web sites, couldn't it just be directed to cygwin or cygwin-xfree? Keith -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple B

RE: Speaking of debian cygwin

2001-12-04 Thread Kevin Schnitzius
http://slashdot.org/article.pl?sid=01/12/04/1355238 Extra '8' in the mail. Kevin -Original Message- From: Randall R Schulz [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 04, 2001 16:19 To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Speaking of deb

Re: Speaking of debian cygwin

2001-12-04 Thread Randall R Schulz
Charles, Are they so upset they got the article pulled? All I get, beyond the Slahsdot page adornments, is this: "Nothing for you to see here. Please move along." Has this article been pulled, or is there an error in the URL you gave? Randall Schulz Mountain View, CA USA At 11:52 2

Re: Speaking of debian cygwin

2001-12-04 Thread Christopher Faylor
On Tue, Dec 04, 2001 at 02:52:34PM -0500, Charles Wilson wrote: >There's another slashdot article: > >http://slashdot.org/article.pl?sid=01/12/04/13552388 > >Seems the debian-devel folks aren't too happy about this... I'm surprised that this has actually finally happened. This has been in discus

Re: Speaking of debian cygwin

2001-12-04 Thread Michael F. March
I read all that and I still can not figure out what the EXACT issue is they have? GNU software running on Windows? DPKG specifically being ported to Windows? After reading all the /. and debian mailing list posts, I *still* can not tell.. > There's another slashdot article: > >

Speaking of debian cygwin

2001-12-04 Thread Charles Wilson
There's another slashdot article: http://slashdot.org/article.pl?sid=01/12/04/13552388 Seems the debian-devel folks aren't too happy about this... --Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: