> At 02:22 PM 1/5/2005, you wrote:
> >If those 'experienced' users are that fed up with
> participating in the project then perhaps they should just
> take a deep breath and avoid sending a response to those
> questions at all. Sometimes silence is better.
>
> And there's the rub. Sometimes s
> Dave Korn wrote:
>
> > How apposite that, in audio terms, "feedback" is
> synonymous with "a
> > loud whining noise"!
>
> Except that in audio, negative feedback is the kind you want. :)
>
...until you're READY TO ROCK!
--
Gary R. Van Sickle
--
Unsubscribe info: http://cy
At 02:22 PM 1/5/2005, you wrote:
>If those 'experienced' users are that fed up with participating in the project
>then perhaps they should just take a deep breath and avoid sending a response
>to those questions at all. Sometimes silence is better.
And there's the rub. Sometimes silence is bet
Dave Korn wrote:
How apposite that, in audio terms, "feedback" is synonymous with "a loud
whining noise"!
Except that in audio, negative feedback is the kind you want. :)
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Doc
Hughes, Bill wrote:
Christopher Faylor wrote:
On Wed, Jan 05, 2005 at 11:02:54AM +0100, Corinna Vinschen wrote:
The bottom line is, you can complain, but the better solution is to
make your environment more foolproof against changes in one part of
it. In case of MSDEV tools I suggest to put the MSD
> -Original Message-
> From: cygwin-owner On Behalf Of Isaac Foraker
> Sent: 04 January 2005 22:27
> I'll be plain. I try to contribute feedback to open source projects
> that I use.
How apposite that, in audio terms, "feedback" is synonymous with "a loud
whining noise"!
chee
Christopher Faylor wrote:
> On Wed, Jan 05, 2005 at 11:02:54AM +0100, Corinna Vinschen wrote:
>> The bottom line is, you can complain, but the better solution is to
>> make your environment more foolproof against changes in one part of
>> it. In case of MSDEV tools I suggest to put the MSDEV tool p
On Wed, Jan 05, 2005 at 11:02:54AM +0100, Corinna Vinschen wrote:
>The bottom line is, you can complain, but the better solution is to
>make your environment more foolproof against changes in one part of it.
>In case of MSDEV tools I suggest to put the MSDEV tool path in front of
>the Cygwin paths.
On Jan 4 17:17, Sam Steingold wrote:
> > * Corinna Vinschen <[EMAIL PROTECTED]> [2004-12-23 10:35:16 +0100]:
> >> My temporary fix for my developers is to remove coreutils `link' from
> >> our systems,
>
> that's what I had to do too.
>
> >> but if it is reinstalled every time coreutils is
> >>
On Tue, Jan 04, 2005 at 03:26:58PM -0700, Isaac Foraker wrote:
> I am, however, greatly disappointed at how negatively certain members of
> this list treat people who provide feedback.
Try to ignore it. There are others out there just ignoring it too.
> Not being able to keep up
> with the vol
I'll be plain. I try to contribute feedback to open source projects
that I use. I've had my own projects, and know how hard it is to get
feedback. I like Cygwin. It lets me switch between Unix and Windows
configurations relatively easily.
I am, however, greatly disappointed at how negativel
> * Corinna Vinschen <[EMAIL PROTECTED]> [2004-12-23 10:35:16 +0100]:
>
>> My temporary fix for my developers is to remove coreutils `link' from
>> our systems,
that's what I had to do too.
>> but if it is reinstalled every time coreutils is
>> upgraded, this will cause an ongoing problem.
indee
On Tue, Jan 04, 2005 at 09:50:02AM -0700, Isaac Foraker wrote:
>That's a really nice attitude. I don't expect anyone to bend over
>backwards, but a little QC would be nice. If you would prefer that
>professionals using Cygwin with commercial configurations do not provide
>feedback, I suggest y
That's a really nice attitude. I don't expect anyone to bend over
backwards, but a little QC would be nice. If you would prefer that
professionals using Cygwin with commercial configurations do not provide
feedback, I suggest you update the fact and just say so.
IF
Christopher Faylor wrote:
O
On Tue, Dec 28, 2004 at 11:15:09PM -0700, Isaac Foraker wrote:
>Well, rather than hacking my build system, I've opted to build my own
>installer for Cygwin the does not contain programs that are causing me
>grief. I know that some people don't want to hear that we use MS VC++
>with Cygwin, but
Well, rather than hacking my build system, I've opted to build my own
installer for Cygwin the does not contain programs that are causing me
grief. I know that some people don't want to hear that we use MS VC++
with Cygwin, but hey, this is the real world here. Cygwin helps our
productivity,
Corinna Vinschen wrote:
The link tool is installed by default on Linux as well.
Well, no one uses VC++ on Linux :-). But this is a problem with other
tools as well (e.g. the gcc distribution included gcj and a bastard
"jar" command for a while, till Gerrit (fortunately) axed it).
Just make sure
On Dec 22 14:54, Isaac Foraker wrote:
> The recent change of installing coreutils with `link.exe' has introduced
> a *new* problem with configurations using Microsoft Visual C++ with
> Cygwin's GNU `make'. Previously, one could specify "LD=link" in a
> Makefile, but now the corutils `link' will
The recent change of installing coreutils with `link.exe' has introduced
a *new* problem with configurations using Microsoft Visual C++ with
Cygwin's GNU `make'. Previously, one could specify "LD=link" in a
Makefile, but now the corutils `link' will supplant Microsoft's linker,
breaking builds
19 matches
Mail list logo
