public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Michael A Chase" <mchase@ix.netcom.com>
To: "Rajat Bawa" <bawarajat@noida.hcltech.com>, "cygwin" <cygwin@cygwin.com>
Subject: Re: failure notice
Date: Mon, 28 Jan 2002 14:39:00 -0000	[thread overview]
Message-ID: <008201c1a84c$79100b40$0d00a8c0@mchasecompaq> (raw)
In-Reply-To: <E04CF3F88ACBD5119EFE00508BBB2121015639E4@exch-01.noida.hcltech.com>

Try the ones you are interested in and see.

Please make any more such enquires to cygwin@cygwin.com, that's where this
belongs unless you are offering patches to fix problems you have found.

--
Mac :})
** I normally forward private questions to the appropriate mail list. **
Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.
----- Original Message -----
From: "Rajat Bawa" <bawarajat@noida.hcltech.com>
To: <cygwin-apps@cygwin.com>
Sent: Monday, January 28, 2002 02:31
Subject: FW: failure notice


> Just wanted to know the support of the Cygwin utilities for
>
> - Files with Japanese "data" &
> - Files with "Japanese filenames"





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

       reply	other threads:[~2002-01-28 14:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E04CF3F88ACBD5119EFE00508BBB2121015639E4@exch-01.noida.hcltech.com>
2002-01-28 14:39 ` Michael A Chase [this message]
2019-03-02 17:38 Failure notice Andy Perkins
2019-03-02 17:39 ` cygwinautoreply
     [not found] <CAH8yC8nrV4i1wOzeBbXDKMJpdfsN-8ZubiN=R7Yow4cBDmG5wQ@mail.gmail.com>
     [not found] ` <5ad17051.cf55650a.73c5d.c3e7SMTPIN_ADDED_MISSING@mx.google.com>
2018-04-14  3:11   ` failure notice Jeffrey Walton
2018-04-14  3:51     ` Brian Inglis
2018-04-14  5:00       ` R0b0t1
2018-04-14  7:27         ` David Stacey
2018-04-14 15:08         ` Brian Inglis
     [not found] <56619fc2.83c1420a.10961.ffffb37fSMTPIN_ADDED_MISSING@mx.google.com>
2015-12-04 14:20 ` Fwd: " Tom Kacvinsky
2015-12-07 14:01   ` Tom Kacvinsky
     [not found] <5644019f.42dc420a.272e2.5d14SMTPIN_ADDED_MISSING@mx.google.com>
2015-11-12  3:07 ` Mario Roy
     [not found] <CAG=EhJo-oJEFqnmYsuNgewpkq1kpJNnaEbs9AxgKRcfuOZkVjg@mail.gmail.com>
     [not found] ` <545ee223.ea5f460a.2b39.ffff870aSMTPIN_ADDED_MISSING@mx.google.com>
2014-11-09  3:43   ` Theodore Si
     [not found] <CAC8hJujotv3avbCppCX5sOfWjiVJmExfORgtLpKXQ6=eOtgmUQ@mail.gmail.com>
     [not found] ` <4e49a66c.02b7960a.199e.ffffeaaeSMTPIN_ADDED@mx.google.com>
2011-08-15 23:08   ` Gary
  -- strict thread matches above, loose matches on Subject: below --
2009-07-10 14:16 _
2002-09-07 22:48 Fred_Smith
1999-07-22 23:56 Teun Burgers
1999-07-26 10:31 ` Chris Faylor
1999-07-31 18:34   ` Chris Faylor
1999-07-31 18:34 ` Teun Burgers

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='008201c1a84c$79100b40$0d00a8c0@mchasecompaq' \
    --to=mchase@ix.netcom.com \
    --cc=bawarajat@noida.hcltech.com \
    --cc=cygwin@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).