From: David Kastrup <dak@gnu.org>
To: git@vger.kernel.org
Subject: Stupid quoting...
Date: Wed, 13 Jun 2007 13:30:49 +0200 [thread overview]
Message-ID: <86ir9sw0pi.fsf@lola.quinscape.zz> (raw)
Hi,
what is the point in quoting file names and their characters in
git-diff's output? And what is the recommended way of undoing the
damage?
I have something like
git-diff -M -C --name-status -r master^ master | {
while read -r flag name
do
case "$name" in *\\[0-3][0-7][0-7]*)
name=$(echo -e $(echo "$name"|sed 's/\\\([0-3][0-7][0-7]\)/\\0\1/g;s/\\\([^0]\)/\\\\\1/g'))
esac
[...]
in order to get through the worst with utf-8 file names, and it is a
complete nuisance (double quotemarks are treated later).
Is there any utility or pipe or invocation that can take a sequence of
filenames as printed by git and turn them back into what they actually
were in the first place?
--
David Kastrup
next reply other threads:[~2007-06-13 11:43 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 11:30 David Kastrup [this message]
2007-06-13 12:06 ` Stupid quoting Alex Riesen
2007-06-13 12:21 ` Johannes Schindelin
[not found] ` <86ejkgvxmb.fsf@lola.quinscape.zz>
2007-06-14 0:51 ` Johannes Schindelin
2007-06-14 6:12 ` David Kastrup
2007-06-14 7:06 ` Alex Riesen
[not found] ` <86hcpb6lr6.fsf@lola.quinscape.zz>
2007-06-14 8:51 ` Alex Riesen
2007-06-14 1:06 ` Steven Grimm
2007-06-14 1:12 ` Johannes Schindelin
2007-06-14 1:19 ` Steven Grimm
2007-06-14 1:34 ` Johannes Schindelin
2007-06-14 8:49 ` Junio C Hamano
2007-06-16 21:03 ` Jakub Narebski
2007-06-18 8:00 ` David Kastrup
2007-06-18 16:19 ` Jeff King
2007-06-19 1:00 ` Johannes Schindelin
2007-06-19 7:44 ` David Kastrup
2007-06-19 9:50 ` Johannes Schindelin
2007-06-19 20:53 ` Olivier Galibert
[not found] ` <86645kutow.fsf@lola.quinscape.zz>
2007-06-20 2:19 ` Johannes Schindelin
2007-06-20 6:19 ` Junio C Hamano
2007-06-20 7:49 ` David Kastrup
2007-06-20 8:40 ` Jakub Narebski
2007-06-20 8:59 ` David Kastrup
2007-06-24 6:50 ` Jan Hudec
2007-06-24 11:14 ` Robin Rosenberg
2007-06-24 11:47 ` Junio C Hamano
2007-06-24 11:58 ` David Kastrup
2007-06-24 12:19 ` Junio C Hamano
2007-06-24 12:41 ` Jeff King
2007-06-24 16:25 ` Jan Hudec
2007-06-24 19:39 ` Robin Rosenberg
2007-06-24 19:47 ` David Kastrup
2007-06-24 20:17 ` Robin Rosenberg
2007-06-24 20:25 ` David Kastrup
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=86ir9sw0pi.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--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).