From: Dave Abrahams <dave@boostpro.com>
To: git@vger.kernel.org
Subject: Bug with URL-decoding
Date: Thu, 6 May 2010 22:06:50 +0000 (UTC) [thread overview]
Message-ID: <loom.20100507T000406-241@post.gmane.org> (raw)
$ cd /tmp
$ mkdir x+y
$ cd x+y
$ git init
$ cd ..
$ git clone file:///tmp/x%2By zz # <==== ERROR
$ git clone file:///tmp/x+y zz # <====== OK
Funny characters do come up in names, especially in test suites
next reply other threads:[~2010-05-06 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 22:06 Dave Abrahams [this message]
2010-05-23 9:16 ` Bug with URL-decoding Jeff King
2010-05-23 9:17 ` [PATCH 1/2] make url-related functions reusable Jeff King
2010-05-23 9:19 ` [PATCH 2/2] decode file:// and ssh:// URLs Jeff King
2010-05-27 10:50 ` Ilari Liusvaara
2010-05-30 5:30 ` Jeff King
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=loom.20100507T000406-241@post.gmane.org \
--to=dave@boostpro.com \
--cc=git@vger.kernel.org \
/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 NNTP newsgroup(s).