From: Joey Hess <joey@kitenet.net>
To: git@vger.kernel.org
Subject: Re: git check-attr -z and quoting
Date: Tue, 2 Nov 2010 18:10:29 -0400 [thread overview]
Message-ID: <20101102221029.GA3646@gnu.kitenet.net> (raw)
In-Reply-To: <7583D61F-64FA-44A8-B5C5-6E0FC329ED32@sb.org>
[-- Attachment #1: Type: text/plain, Size: 764 bytes --]
Kevin Ballard wrote:
> On Nov 2, 2010, at 8:57 AM, Joey Hess wrote:
>
> > First, thanks to all for supporting -z in various commands like
> > git ls-files and git diff. Big help for plumbing, as I'm sure you know.
> >
> > But, git check-attr -z only enables NUL separation of its input; output
> > always has munged pathnames. This bit me trying to use it as plumbing.
>
> What do you mean by munged pathnames? As long as the path doesn't contain the sequence ": " it seems like the output should be unambiguous.
Quoted with quote_c_style()
$ perl -e 'print shift()."\n\0"' '¡hello!' | git check-attr eol -z --stdin
"\302\241hello!\n": foo: unspecified
Maybe -Z could enable this output:
¡hello!\n\0foo\0unspecified\0
--
see shy jo
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2010-11-02 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 15:57 git check-attr -z and quoting Joey Hess
2010-11-02 21:24 ` Kevin Ballard
2010-11-02 22:10 ` Joey Hess [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=20101102221029.GA3646@gnu.kitenet.net \
--to=joey@kitenet.net \
--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).