From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: "cygwin-talk@cygwin.com" <cygwin-talk@cygwin.com>
Subject: RE: Bug: cygport fails when the working directory pathname contains spaces
Date: Wed, 27 Jan 2010 16:30:00 -0000 [thread overview]
Message-ID: <0105D5C1E0353146B1B222348B0411A208B26372C0@NIHMLBX02.nih.gov> (raw)
In-Reply-To: <20100127161844.GA29928@ednor.casa.cgf.cx>
Christopher Faylor sent the following at Wednesday, January 27, 2010 11:19 AM
>And, the most important point here is that what Yaakov does isn't a
>"job". It's a volunteer effort. A gift. He can decide what he does or
>doesn't do and insisting that he isn't doing his job because he doesn't
>want to perform a pointless exercise seems rather rude to me.
Actually, I'm a little disappointed. I don't recall "WJM" being used in
a response for quite a while now. Indeed, it had fallen so fall off my
radar screen that the other day I forgot to use it when it should have
been part of a post.
Please. Let's not let this cygwin tradition be abandoned.
- Barry
Disclaimer: Statements made herein are not made on behalf of NIAID.
next prev parent reply other threads:[~2010-01-27 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B5FA03C.8020504@monai.ca>
[not found] ` <4B5FC41E.6090301@users.sourceforge.net>
[not found] ` <4B5FD16E.4060107@monai.ca>
[not found] ` <4B5FF5AE.3050904@users.sourceforge.net>
[not found] ` <op.u66ni3hb1e62zd@merlin.emma.line.org>
[not found] ` <4B600397.8030505@users.sourceforge.net>
[not found] ` <2BF01EB27B56CC478AD6E5A0A28931F2A68982@A1DAL1SWPES19MB.ams.acs-inc.net>
2010-01-27 15:52 ` Buchbinder, Barry (NIH/NIAID) [E]
[not found] ` <20100127161844.GA29928@ednor.casa.cgf.cx>
2010-01-27 16:30 ` Buchbinder, Barry (NIH/NIAID) [E] [this message]
2010-01-27 17:13 ` Christopher Faylor
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=0105D5C1E0353146B1B222348B0411A208B26372C0@NIHMLBX02.nih.gov \
--to=bbuchbinder@niaid.nih.gov \
--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).