public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-talk@cygwin.com
Subject: Re: Cygwin mentioned in "current directory" discussion
Date: Thu, 25 Nov 2010 08:32:00 -0000	[thread overview]
Message-ID: <20101125082956.GL18309@calimero.vinschen.de> (raw)
In-Reply-To: <4CEDD6C8.7090201@gmail.com>

On Nov 25 03:23, Dave Korn wrote:
> On 16/11/2010 19:52, Corinna Vinschen wrote:
> 
> > And now he deleted my reply to f0dder as well, giving the reason
> > "Discussing undocumented APIs is a good way to get a comment deleted"
> 
>   Suppressing undocumented APIs is what got MS sued to hell and back by every
> monopoly department from here to Singapore, isn't it?  They should really
> learn not to look like they're trying to hide stuff.
> 
> > and he closed the blog entry for further commenting.  
> 
>   Corporate drone.
> 
> > Nice guy.
> 
>   I beg to differ.  Say, exactly what are the limits on the use of language on
> this list, anyway?

Don't use dirty language, except in dirty circumstances.  Live and let
live, even lawyers.  In general, follow the ideals of hippokind.

But woe betide you if you talk about the cygwin_internal() API in public!


Corinna

  reply	other threads:[~2010-11-25  8:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10  4:38 Christopher Faylor
2010-11-15 19:27 ` Corinna Vinschen
2010-11-15 21:35   ` Andy Koppe
2010-11-16  8:30     ` Corinna Vinschen
2010-11-16 16:11       ` Christopher Faylor
2010-11-16 19:54         ` Corinna Vinschen
2010-11-16 21:10           ` Christopher Faylor
2010-11-25  2:59           ` Dave Korn
2010-11-25  8:32             ` Corinna Vinschen [this message]
2010-11-27 11:20           ` Gary
2010-11-27 19:13             ` Christopher Faylor
2010-11-30  9:37               ` Gary

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=20101125082956.GL18309@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --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).