Wading in piles of hippo dung...

Wading in piles of hippo dung...

[mwoehlke]

Do we keep records anywhere for 'longest-running thread', 'deepest 
thread', etc? All the 'make broke' whiners have (so far) produced a 
thread with 90 post (65 in cygwin, 25 in cygwin-talk) that is 25 levels 
deep. :-) And that doesn't count the other threads...

Hmm, depth = number of posts in -talk... coincidence?

Nope, it's all CGF's evil fault. :-D

-- 
Matthew
vIMprove your life! Now on version 7!

Re: Wading in piles of hippo dung...

[Christopher Faylor]

On Wed, Aug 16, 2006 at 04:42:54PM -0500, mwoehlke wrote:
>Do we keep records anywhere for 'longest-running thread', 'deepest
>thread', etc?  All the 'make broke' whiners have (so far) produced a
>thread with 90 post (65 in cygwin, 25 in cygwin-talk) that is 25 levels
>deep.  :-) And that doesn't count the other threads...
>
>Hmm, depth = number of posts in -talk...  coincidence?
>
>Nope, it's all CGF's evil fault.  :-D

No matter what we do, it will never hold a candle to the long-running discussion
about questionable content in cygwin's fortune.  I actually asked for feedback
for that one and boy did I ever get it.

cgf

Re: Wading in piles of hippo dung...

[Brian Dessent]

mwoehlke wrote:

> Do we keep records anywhere for 'longest-running thread', 'deepest
> thread', etc? All the 'make broke' whiners have (so far) produced a
> thread with 90 post (65 in cygwin, 25 in cygwin-talk) that is 25 levels
> deep. :-) And that doesn't count the other threads...
> 
> Hmm, depth = number of posts in -talk... coincidence?
> 
> Nope, it's all CGF's evil fault. :-D

It's times like this that I think Cygwin needs an official drinking
game...

* Every time someone starts a new thread to report that upgrading to
make 3.81 broke something that uses MS DOS paths, take a sip.  (Take a
chug if they report it to the -apps list.)

* Every time someone has a problem with SSHD and hasn't run
ssh-host-config, take a sip.  (Take a chug if they mention pigtail.net.)

* Every time someone asks when the next release of cygwin1.dll is coming
out, take a sip.  (Take a chug if they're asking about a well-known
problem that has been fixed in CVS/snapshots for a while.)

* Every time someone asks how to get some ancient and/or obsolete
version of some package, take a sip.  (Take a chug if they're using
B20.)

* Every time someone reports a benign SIGSEGV in gdb, take a sip.

* Every time someone asks for help with a problem that turns out to be
caused by not having some required package installed, but doesn't post
cygcheck output that would have shown from the get-go that they were
missing that package, take a long chug.

* Every time some random problem turns out to be caused by some stupid
dos/unix line-endings issue, take a sip.

* Every time someone tries to use a bash-ism in a /bin/sh script that is
run by /bin/ash, take a sip (included for posterity's sake.)

* Every time someone runs into what seems to be a legitmate,
reproducible bug but instead of trying to figure out why it's happening
so that it can be fixed uses a workaround such as sticking to an older
version, take a long chug.

* Every time someone tries to use the native gcc to cross compile, take
a sip.  Take a long, hard chug if they try to execute a foreign ELF
binary under Cygwin.

* Every time someone refers to the mailing list as a forum, newsgroup,
etc., take a sip.

* Every time someone thinks that the mount table should be edited via
REGEDIT and is oblivious to mount/umount, take a sip.

* Every time someone tries to link cygwin and -mno-cygwin object files
together in the same binary and encounters problems, take a sip.

* Every time someone has problems accessing a network resource over
pubkey authenticated ssh, take a sip.  (Take a chug if they say they've
read the FAQ, users guide, and searched the archives with no solution.)

* Every time someone posts on the -xfree list trying to use X over ssh
without the -Y or -X option, take a sip.

* Every time someone tries to use a native console program in rxvt and
encounters weirdness, take a sip.

* Every time someone asks "where is FOO" or "what package has BAR" take
a sip.

* Every time someone reports an error building some random obscure
tarball and assumes that everyone knows what he's talking about without
providing any details, take a sip.  Take a chug if all they report is
the 'make' erroring out (last line of the build output).

* Every time someone rephrases an error message in their own words
instead of just copying and pasting the exact thing, take a sip.  Take a
chug if they instead attach a screen shot of the console.  Take a really
long chug if it's in the form of an uncompressed BMP.

* Every time someone replies in a thread with something completely and
totally unrelated but thinks that changing the subject line is
sufficient to start a new thread, take a sip.

* Every time someone includes a reference to something muttered on the
mailing list 7 years ago that no longer applies to versions released in
the last few years, take a sip.

* Every time someone encounters a piece of software whose build was only
really ever tested on linux and is casual about the ordering of -libs in
the link command or the $EXESUFFIX, take a sip.

* Every time someone gets a link error when trying to compile C++ code
using 'gcc' instead of 'g++', take a sip.  Take a chug if they were
trying to call ld directly to link.

* Every time someone asks a generic scripting-ish question and gets
dozens of replies each touting their own pet solution, and a long thread
evolves with back and forth debating of the merits of proper quoting for
filenames with spaces, the efficiency of xargs, the proper use of
regular expressions, etc. then take a long chug.

* Every time a third party distribution of binaries without source is
spotted and an ensuing GPL semantics debate breaks out, take a chug.

* Every time that a "bike shed" thread occurs (i.e. lots of talking and
zero action) after someone reports that Cygwin is too slow or is too
hard to use/comprehend, then take a very long chug.

* Every time someone asks for a [cygwin] to be automatically added to
the subject, or the Reply-to set to the list, take a sip.

* Every time that cgf's sarcasm or lack of patience becomes the focus of
an otherwise-technical thread, take a sip.  Take a chug if somehow Red
Hat is mentioned as having relevancy.

* EVERY TIME THAT A HIPPO IS MENTIONED, FINISH YOUR DRINK AND GET A NEW
ONE.

Brian

RE: Wading in piles of hippo dung...

[Dave Korn]

On 16 August 2006 23:45, Brian Dessent wrote:

> mwoehlke wrote:
> 
>> Do we keep records anywhere for 'longest-running thread', 'deepest
>> thread', etc? All the 'make broke' whiners have (so far) produced a
>> thread with 90 post (65 in cygwin, 25 in cygwin-talk) that is 25 levels
>> deep. :-) And that doesn't count the other threads...
>> 
>> Hmm, depth = number of posts in -talk... coincidence?
>> 
>> Nope, it's all CGF's evil fault. :-D
> 
> It's times like this that I think Cygwin needs an official drinking
> game...
> 
> * Every time someone [ ... snip ... ]

  <hic>  Thatsh a greaaaat game!!1!2!!3!  But I think my liver hatesh you! :-/


> * EVERY TIME THAT A HIPPO IS MENTIONED, FINISH YOUR DRINK AND GET A NEW
> ONE.

  Including that time?  <glug>

  BTW, you left one out:

* Every time someone builds dkpg or rpm and reports that it doesn't work, take
a sip.  If they suggest switching over the entire distro to use dpkg or rpm,
in order to make it work, take a glug.

  :-)

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....

Re: Wading in piles of hippo dung...

[Christopher Faylor]

On Wed, Aug 16, 2006 at 03:44:32PM -0700, Brian Dessent wrote:
>mwoehlke wrote:
>
>> Do we keep records anywhere for 'longest-running thread', 'deepest
>> thread', etc? All the 'make broke' whiners have (so far) produced a
>> thread with 90 post (65 in cygwin, 25 in cygwin-talk) that is 25 levels
>> deep. :-) And that doesn't count the other threads...
>> 
>> Hmm, depth = number of posts in -talk... coincidence?
>> 
>> Nope, it's all CGF's evil fault. :-D
>
>It's times like this that I think Cygwin needs an official drinking
>game...
>
>* Every time someone starts a new thread to report that upgrading to
>make 3.81 broke something that uses MS DOS paths, take a sip.  (Take a
>chug if they report it to the -apps list.)
>
>* Every time someone has a problem with SSHD and hasn't run
>ssh-host-config, take a sip.  (Take a chug if they mention pigtail.net.)
>
>* Every time someone asks when the next release of cygwin1.dll is coming
>out, take a sip.  (Take a chug if they're asking about a well-known
>problem that has been fixed in CVS/snapshots for a while.)
>
>* Every time someone asks how to get some ancient and/or obsolete
>version of some package, take a sip.  (Take a chug if they're using
>B20.)
>
>* Every time someone reports a benign SIGSEGV in gdb, take a sip.
>
>* Every time someone asks for help with a problem that turns out to be
>caused by not having some required package installed, but doesn't post
>cygcheck output that would have shown from the get-go that they were
>missing that package, take a long chug.
>
>* Every time some random problem turns out to be caused by some stupid
>dos/unix line-endings issue, take a sip.
>
>* Every time someone tries to use a bash-ism in a /bin/sh script that is
>run by /bin/ash, take a sip (included for posterity's sake.)
>
>* Every time someone runs into what seems to be a legitmate,
>reproducible bug but instead of trying to figure out why it's happening
>so that it can be fixed uses a workaround such as sticking to an older
>version, take a long chug.
>
>* Every time someone tries to use the native gcc to cross compile, take
>a sip.  Take a long, hard chug if they try to execute a foreign ELF
>binary under Cygwin.
>
>* Every time someone refers to the mailing list as a forum, newsgroup,
>etc., take a sip.
>
>* Every time someone thinks that the mount table should be edited via
>REGEDIT and is oblivious to mount/umount, take a sip.
>
>* Every time someone tries to link cygwin and -mno-cygwin object files
>together in the same binary and encounters problems, take a sip.
>
>* Every time someone has problems accessing a network resource over
>pubkey authenticated ssh, take a sip.  (Take a chug if they say they've
>read the FAQ, users guide, and searched the archives with no solution.)
>
>* Every time someone posts on the -xfree list trying to use X over ssh
>without the -Y or -X option, take a sip.
>
>* Every time someone tries to use a native console program in rxvt and
>encounters weirdness, take a sip.
>
>* Every time someone asks "where is FOO" or "what package has BAR" take
>a sip.
>
>* Every time someone reports an error building some random obscure
>tarball and assumes that everyone knows what he's talking about without
>providing any details, take a sip.  Take a chug if all they report is
>the 'make' erroring out (last line of the build output).
>
>* Every time someone rephrases an error message in their own words
>instead of just copying and pasting the exact thing, take a sip.  Take a
>chug if they instead attach a screen shot of the console.  Take a really
>long chug if it's in the form of an uncompressed BMP.
>
>* Every time someone replies in a thread with something completely and
>totally unrelated but thinks that changing the subject line is
>sufficient to start a new thread, take a sip.
>
>* Every time someone includes a reference to something muttered on the
>mailing list 7 years ago that no longer applies to versions released in
>the last few years, take a sip.
>
>* Every time someone encounters a piece of software whose build was only
>really ever tested on linux and is casual about the ordering of -libs in
>the link command or the $EXESUFFIX, take a sip.
>
>* Every time someone gets a link error when trying to compile C++ code
>using 'gcc' instead of 'g++', take a sip.  Take a chug if they were
>trying to call ld directly to link.
>
>* Every time someone asks a generic scripting-ish question and gets
>dozens of replies each touting their own pet solution, and a long thread
>evolves with back and forth debating of the merits of proper quoting for
>filenames with spaces, the efficiency of xargs, the proper use of
>regular expressions, etc. then take a long chug.
>
>* Every time a third party distribution of binaries without source is
>spotted and an ensuing GPL semantics debate breaks out, take a chug.
>
>* Every time that a "bike shed" thread occurs (i.e. lots of talking and
>zero action) after someone reports that Cygwin is too slow or is too
>hard to use/comprehend, then take a very long chug.
>
>* Every time someone asks for a [cygwin] to be automatically added to
>the subject, or the Reply-to set to the list, take a sip.
>
>* Every time that cgf's sarcasm or lack of patience becomes the focus of
>an otherwise-technical thread, take a sip.  Take a chug if somehow Red
>Hat is mentioned as having relevancy.
>
>* EVERY TIME THAT A HIPPO IS MENTIONED, FINISH YOUR DRINK AND GET A NEW
>ONE.

I have to say that I can't support Brian's game.

With total attention to the above rules we'd all be alcoholics.

cgf

Re: Wading in piles of hippo dung...

[mwoehlke]

Christopher Faylor wrote:
> On Wed, Aug 16, 2006 at 04:42:54PM -0500, mwoehlke wrote:
>> Do we keep records anywhere for 'longest-running thread', 'deepest
>> thread', etc?  All the 'make broke' whiners have (so far) produced a
>> thread with 90 post (65 in cygwin, 25 in cygwin-talk) that is 25 levels
>> deep.  :-) And that doesn't count the other threads...
>>
>> Hmm, depth = number of posts in -talk...  coincidence?
>>
>> Nope, it's all CGF's evil fault.  :-D
> 
> No matter what we do, it will never hold a candle to the long-running discussion
> about questionable content in cygwin's fortune.  I actually asked for feedback
> for that one and boy did I ever get it.

Oh, wow... yeah, I can only *imagine* the can of worms that would have 
opened. :-)

-- 
Matthew
vIMprove your life! Now on version 7!

Re: Wading in piles of hippo dung...

[Christopher Faylor]

This is fun.

On Thu, Aug 17, 2006 at 12:08:37AM +0100, Dave Korn wrote:
>* Every time someone builds dkpg or rpm and reports that it doesn't work, take
>a sip.  If they suggest switching over the entire distro to use dpkg or rpm,
>in order to make it work, take a glug.

How about:

* Every time someone responds to a thread which is older than a week
with information that has already been given, take a sip.  If the thread
is older than a month, take a chug.

cgf

Re: Wading in piles of hippo dung...

[mwoehlke]

Brian Dessent wrote a cygwin drinking game...

Brian, you have too much time on your hands. :-)

-- 
Matthew
vIMprove your life! Now on version 7!

Re: Wading in piles of hippo dung...

[Igor Peshansky]

On Wed, 16 Aug 2006, Brian Dessent wrote:

> mwoehlke wrote:
>
> > Do we keep records anywhere for 'longest-running thread', 'deepest
> > thread', etc? All the 'make broke' whiners have (so far) produced a
> > thread with 90 post (65 in cygwin, 25 in cygwin-talk) that is 25 levels
> > deep. :-) And that doesn't count the other threads...
> >
> > Hmm, depth = number of posts in -talk... coincidence?
> >
> > Nope, it's all CGF's evil fault. :-D
>
> It's times like this that I think Cygwin needs an official drinking
> game...
>
> [snip the totally hilarious but absolutely unrealistic set of rules]

because where would Cygwin be with all core developers lying happy drunk
on their keyboards while they should be busily resurrecting MS-DOS path
handling in make?
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

Re: Wading in piles of hippo dung...

[Igor Peshansky]

On Wed, 16 Aug 2006, mwoehlke wrote:

> Brian Dessent wrote a cygwin drinking game...
>
> Brian, you have too much time on your hands. :-)

No, someone with *too* much time on their hands would write a desktop
notifier applet that would sit in the system tray, monitor the Cygwin
mailing lists, and *remind* you to take a sip, a chug, or a glug...
	Igor
P.S. But a pointer to that drinking game thread should be saved for
posterity.  Wasn't someone keeping a page of Cygwin mailing list funnies?
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

Re: Wading in piles of hippo dung...

[Corinna Vinschen]

On Aug 16 20:21, Igor Peshansky wrote:
> On Wed, 16 Aug 2006, mwoehlke wrote:
> 
> > Brian Dessent wrote a cygwin drinking game...
> >
> > Brian, you have too much time on your hands. :-)
> 
> No, someone with *too* much time on their hands would write a desktop
> notifier applet that would sit in the system tray, monitor the Cygwin
> mailing lists, and *remind* you to take a sip, a chug, or a glug...
> 	Igor
> P.S. But a pointer to that drinking game thread should be saved for
> posterity.

I second that.  We should create a "The Cygwin Drinking Game" page
on cygwin.com.  The game is a bit dangerous, maybe, but Cygwin is
only for the daring amoungst us anyway.


Corinna