public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: mwoehlke <mwoehlke@tibco.com>
To: cygwin-talk@cygwin.com
Subject: Re: Cygintl-3.dll was not found
Date: Thu, 10 Aug 2006 20:25:00 -0000	[thread overview]
Message-ID: <ebg4gj$39g$2@sea.gmane.org> (raw)
In-Reply-To: <20060810195325.GB935@trixie.casa.cgf.cx>

Christopher Faylor wrote:
> On Thu, Aug 10, 2006 at 10:13:26AM -0500, mwoehlke wrote:
>> Christopher Faylor wrote:
>>> So what kind of response would you expect to my mail?  More "thin
>>> intelligence", "foolish" responses?
>> Are you asking if I thought your response was reasonable and 
>> non-inflammatory (yes; it helped /me/ step back and start thinking again 
>> :-)), or if I think infoterror is a troll? Or do I just not understand 
>> the question?
> 
> I was just wondering if we'd get more of the same.  Just an idle question.

Ah. Well then it deserves an idle response. :-)
(Did you miss it? Look closer... ;-))

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

  parent reply	other threads:[~2006-08-10 20:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <58fb98730601070837k26ad68f5l@mail.gmail.com>
     [not found] ` <43BFEFB9.EA24C5B4@dessent.net>
     [not found]   ` <5718434.post@talk.nabble.com>
     [not found]     ` <003001c6bb9a$4e15b140$a501a8c0@CAM.ARTIMI.COM>
     [not found]       ` <5732487.post@talk.nabble.com>
     [not found]         ` <20060809210958.GA3815@trixie.casa.cgf.cx>
2006-08-09 22:34           ` mwoehlke
2006-08-10  0:07             ` Igor Peshansky
2006-08-10  0:37               ` mwoehlke
2006-08-10  9:58               ` Dave Korn
2006-08-10 12:21                 ` Igor Peshansky
2006-08-10  0:54             ` Christopher Faylor
2006-08-10 15:15               ` mwoehlke
2006-08-10 16:04                 ` vIMprovement? (Was Re: Cygintl-3.dll was not found) Igor Peshansky
2006-08-10 17:45                   ` mwoehlke
2006-08-10 19:53                 ` Cygintl-3.dll was not found Christopher Faylor
2006-08-10 20:24                   ` Dave Korn
2006-08-10 20:35                     ` Christopher Faylor
2006-08-10 23:01                     ` mwoehlke
2006-08-10 20:25                   ` mwoehlke [this message]
     [not found]     ` <7022170.post@talk.nabble.com>
     [not found]       ` <7042419.post@talk.nabble.com>
     [not found]         ` <20061028055933.GA19517@trixie.casa.cgf.cx>
     [not found]           ` <7065394.post@talk.nabble.com>
     [not found]             ` <20061029221805.GA1057@trixie.casa.cgf.cx>
     [not found]               ` <7106666.post@talk.nabble.com>
     [not found]                 ` <20061101221317.GA3677@trixie.casa.cgf.cx>
     [not found]                   ` <7124473.post@talk.nabble.com>
2006-11-01 23:46                     ` Cary Jamison
2006-11-02  1:28                       ` Christopher Faylor
2006-11-02  1:43                         ` Christopher Faylor
2006-11-02 19:46                           ` Dave Korn
2006-11-03 16:44                             ` Igor Peshansky
2006-11-02  1:44                         ` Brian Dessent
     [not found] <7308368.post@talk.nabble.com>
2006-11-12 22:39 ` Dave Korn

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='ebg4gj$39g$2@sea.gmane.org' \
    --to=mwoehlke@tibco.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).