From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-talk@cygwin.com
Subject: Re: Cygwin mentioned in "current directory" discussion
Date: Tue, 16 Nov 2010 21:10:00 -0000 [thread overview]
Message-ID: <20101116210930.GB22104@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20101116195202.GA1648@calimero.vinschen.de>
On Tue, Nov 16, 2010 at 08:52:02PM +0100, Corinna Vinschen wrote:
>On Nov 16 11:11, Christopher Faylor wrote:
>> On Tue, Nov 16, 2010 at 09:29:24AM +0100, Corinna Vinschen wrote:
>> >On Nov 15 21:34, Andy Koppe wrote:
>> >> On 15 November 2010 19:26, Corinna Vinschen wrote:
>> >> > On Nov ??9 23:37, Christopher Faylor wrote:
>> >> >> https://blogs.msdn.com/b/oldnewthing/archive/2010/11/09/10087919.aspx
>> >> >
>> >> > This morning I added a comment to the blog, #42 in the list:
>> >> >[...]
>> >> >
>> >> > Two minutes ago, I found that my comment had been silently removed!
>> >> > I'm not aware that my comment contained offensive, abusive, or
>> >> > disrespectful language. I'm really wondering why Raymond decided
>> >> > to remove my comment. This is quite disappointing.
>> >>
>> >> Perhaps it got swallowed by a COM server that can't deal with a
>> >> disappeared working directory. ;)
>> >
>> >Or Raymond fears hippos.
>>
>> He also deleted my response to the guy who suggested that Windows does
>> copy-on-write so we could modify NTDLL. And, now I can't seem to
>> respond at all.
>>
>> Sure. We could just figure out where to modify NTDLL in all of the
>> versions of NTDLL that have ever existed and then stand on our heads
>> to modify the memory in place every time a Cygwin process is started.
>>
>> And, as Corinna says, this all flys in the face of Cygwin's philosophy.
>>
>> Meh.
>
>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"
>and he closed the blog entry for further commenting. Nice guy.
>I don't quite understand the difference between my comments and the
>other comments.
>
>Apart from that I don't understand his weird replies about 0% and 100%
>correctness. Well, I'm not interested in COM anyway. And if COM
>changes the CWD it's broken by design. But I guess that's not allowed
>to say, either...
I didn't get that either. But I wonder which gets more hits: this
mailing list archive or his blog?
cgf
next prev parent reply other threads:[~2010-11-16 21:10 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 [this message]
2010-11-25 2:59 ` Dave Korn
2010-11-25 8:32 ` Corinna Vinschen
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=20101116210930.GB22104@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@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).