public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: One Angry User <angry@lusers.org>
To: The Cygwin-Talk Maiming List <cygwin-talk@cygwin.com>,
	        The Cygwin-Talk Maiming List <cygwin-talk@cygwin.com>
Subject: Re: FW: change in behavior of make from 3.80 to 3.81
Date: Thu, 17 Aug 2006 16:10:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.63.0608171209540.14156@access1.cims.nyu.edu> (raw)
In-Reply-To: <20060817160343.GA22519@trixie.casa.cgf.cx>

On a calm Thursday, the 17th day of August, 2006, Christopher Faylor's computer deigned to emit the following stream of bytes:

> On Thu, Aug 17, 2006 at 05:01:01PM +0100, Dave Korn wrote:
> >On 17 August 2006 16:46, Christopher Faylor wrote:
> >
> >> On Thu, Aug 17, 2006 at 04:13:10PM +0100, Dave Korn wrote:
> >>> On 17 August 2006 16:01, William A. Hoffman wrote:
> >>>
> >>>> At 10:49 AM 8/17/2006, Christopher Faylor wrote:
> >>>>> I've already mentioned once that this was the wrong mailing list for
> >>>>> this. Why do you seem to need everything repeated at you?
> >>>>>
> >>>>> If you, or anyone, is having problems with MinGW's make it would behoove
> >>>>> you to discuss the problems in a mailing list which was populated by
> >>>>> people who are familiar with it.
> >>>>
> >>>> Because I do not agree with your suggestion.
> >>>
> >>>  *sip*
> >>>
> >>>>  Apparently you need things repeated to you.
> >>>
> >>>  *sip*
> >>>
> >>>> So, here is my reason for the post again.
> >>>
> >>>  *sip*
> >>>
> >>>> You mentioned MinGW as an alternative, it does not work.
> >>>> Also, someone on this list asked me a question, and I answered it.
> >>>
> >>> AAAAAARRRRRRRRHRRHRGGGHHHHH   <smashes neck entirely off bottle>  GLUG
> >>> GLUG GLUG  GLUG    GLUG  GLUUURRRRGLE
> >>>
> >>>
> >>>  The stupidity levels emanating from this guy's posts are sucking all the
> >>> intelligence out of my brain, I swear, I can feel it all slipping away from
> >>> me.....
> >>
> >> Me not know what you mean Dave Korn.  Me think you...
> >>
> >> Hmm.  Me lost train of thought.
> >>
> >> Puppies!
> >>
> >> cfg
> >
> >
> >  Oh look!  <points>  An elephant!!!!
> >
> >
> >  <squelch>
> >
> >  Oops.  Poor puppy.   <snifl>
>
> Now me sad.
>
> > <looks around>
> >
> >     oooOOOOOooooOOOO!  Shiny things!
> >
> >   <happy again>
>
> Me not see shiny thing.  Me play with make instead.
>
> Colons not work.
>
> Now me very very sad.

Oh, he who makes -- make my make make sense!

OAU

  parent reply	other threads:[~2006-08-17 16:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-17 15:13 Dave Korn
2006-08-17 15:45 ` Christopher Faylor
2006-08-17 15:50   ` Christopher Faylor
2006-08-17 16:17     ` Igor Peshansky
2006-08-17 16:01   ` Dave Korn
2006-08-17 16:03     ` Christopher Faylor
2006-08-17 16:08       ` Dave Korn
2006-08-17 16:10       ` One Angry User [this message]
2006-08-17 16:01   ` One Angry User
  -- strict thread matches above, loose matches on Subject: below --
2006-08-16  9:49 Dave Korn
2006-08-16 15:04 ` Christopher Faylor
2006-08-16 16:45   ` Charli Li

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=Pine.GSO.4.63.0608171209540.14156@access1.cims.nyu.edu \
    --to=angry@lusers.org \
    --cc=cygwin-talk@cygwin.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).