public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: The Cygwin-Talk Maiming List <cygwin-talk@cygwin.com>
Subject: Re: tar, win-path conversion bug
Date: Thu, 27 Jul 2006 04:08:00 -0000	[thread overview]
Message-ID: <20060727040819.GA19076@trixie.casa.cgf.cx> (raw)
In-Reply-To: <44C83ADB.5060804@byu.net>

On Wed, Jul 26, 2006 at 10:02:35PM -0600, Eric Blake wrote:
>According to Christopher Faylor on 7/26/2006 9:58 PM:
>>>It's certainly not the highest priority on my list.  I would just stick
>>>with POSIX paths.
>>
>>What a crazy idea.
>
>Almost as crazy as the notion of avoiding Windows paths with cygwin
>make.  Who would have thought?

Certainly not me.

But, then, I often want to use Cygwin as a dessert topping, so my use
may not be standard.

cgf

      reply	other threads:[~2006-07-27  4:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <44C6C0B6.9050206@tlinx.org>
     [not found] ` <44C8342A.1070704@byu.net>
     [not found]   ` <20060727035831.GA5943@trixie.casa.cgf.cx>
2006-07-27  4:02     ` Eric Blake
2006-07-27  4:08       ` Christopher Faylor [this message]

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=20060727040819.GA19076@trixie.casa.cgf.cx \
    --to=cgf-no-personal-reply-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).