From: Herbert Xu <herbert@gondor.apana.org.au>
To: Eric Blake <eblake@redhat.com>
Cc: edward@sidefx.com, dash@vger.kernel.org
Subject: Re: [PATCH] Support DOS paths in dash
Date: Thu, 2 Oct 2014 08:41:37 +0800 [thread overview]
Message-ID: <20141002004137.GA23830@gondor.apana.org.au> (raw)
In-Reply-To: <542B2882.9030400@redhat.com>
Eric Blake <eblake@redhat.com> wrote:
>
> I'm not interested in burdening the cygwin build of dash with a one-off
> patch, so I'd like to gauge the upstream thoughts - is it worth
> including platform-specific patches like this (no penalty to build size
> of non-cygwin platforms, and on cygwin, it allows 'cd c:/' to behave as
> shorthand for 'cd /cygdrive/c/')? If the patch lands in dash.git, then
> I'll rebuild the cygwin port of dash to include a backport (rather than
> waiting for 0.5.9 to be released). If there is no interest, I'd rather
> just drop the patch. The cygwin community already states that
> /cygdrive/c notation is the official way to access drive letters, and
> that if 'c:/' works it is nice, but it is not a design goal to always
> have it work.
It's fine by me.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2014-10-02 0:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <announce.4A5C7A2B.4020700@byu.net>
[not found] ` <4B5860C9.50100@sidefx.com>
[not found] ` <4B591221.10501@byu.net>
[not found] ` <4B91105B.7050205@sidefx.com>
[not found] ` <20100305152637.GK7980@calimero.vinschen.de>
[not found] ` <4B913788.40301@sidefx.com>
[not found] ` <4B913AF2.3070102@redhat.com>
[not found] ` <20100305172048.GN7980@calimero.vinschen.de>
[not found] ` <4EDA9E99.9030307@redhat.com>
[not found] ` <51545CD9.4050607@sidefx.com>
2014-09-30 22:02 ` [PATCH] Support DOS paths in dash Eric Blake
2014-10-02 0:41 ` Herbert Xu [this message]
2014-10-02 3:18 ` Edward Lam
2014-10-04 4:07 ` Herbert Xu
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=20141002004137.GA23830@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=dash@vger.kernel.org \
--cc=eblake@redhat.com \
--cc=edward@sidefx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.