From: "Chiedu Oranye" <chiedu7@afn.org>
To: "cygwin" <cygwin@cygwin.com>
Subject: Hello cygwin
Date: Mon, 12 Sep 2016 12:20:00 -0000 [thread overview]
Message-ID: <CF755CCB-07B2-4A03-A434-CBF1790A3C24@afn.org> (raw)
sup cygwin
http://www.cheeringpixels.com/traffic.php?garden=1t7cdcxnkq8ckn61
Chiedu Oranye
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2016-09-12 12:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 12:20 Chiedu Oranye [this message]
[not found] <dev8585g.u66vtmt1.gh4xv.60ax@nhathuocmychau.com>
2019-07-07 18:05 ` hello Cygwin Larry W. Virden
-- strict thread matches above, loose matches on Subject: below --
2018-01-15 20:26 Hello Cygwin allangschrum
2017-01-16 12:08 Hello cygwin Patricia Rowold
2016-12-11 10:14 hello cygwin Chiedu Oranye
2016-02-08 12:42 wdtj
2012-04-22 13:56 Hello cygwin pinkeraser
2012-04-22 18:54 ` Adam Puckett
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=CF755CCB-07B2-4A03-A434-CBF1790A3C24@afn.org \
--to=chiedu7@afn.org \
--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).