From: Junio C Hamano <junkio@cox.net>
To: Paul Eggert <eggert@CS.UCLA.EDU>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: [PATCH] Try URI quoting for embedded TAB and LF in pathnames
Date: Thu, 13 Oct 2005 23:59:09 -0700 [thread overview]
Message-ID: <7vll0wvb2a.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <87vf02qy79.fsf@penguin.cs.ucla.edu> (Paul Eggert's message of "Wed, 12 Oct 2005 13:26:02 -0700")
Paul Eggert <eggert@CS.UCLA.EDU> writes:
> Here is the proposed format. Each file name is a string of bytes, in
> one of the following two formats:
>
> A. A nonempty sequence of ASCII graphic characters (i.e., bytes in
> the range '!' == '\041' through '~' == '\177'). The first byte
> cannot be '!' == '\041' or '"' == '\042'. Leading '"' is used for
> (B) below, and leading '!' is reserved for future extensions.
>
> B. A nonempty C-language character string literal, with the following
> restrictions and modifications:
>
> B1. No multibyte character processing is done. Members of the
> string literal are treated as bytes, not characters. Null
> bytes are not allowed, and '"' == '\042', '\\' == '\134' and
> '\n' == '\012' are allowed only if properly escaped as shown
> below; but all other bytes are allowed.
>
> B2. No trigraph processing is done (e.g., ??/ stands for three
> bytes, not one).
>
> B3. No line-splicing is done (i.e., backslash-newline is not allowed).
>
> B4. Only the following escape sequences are allowed.
>
> \" \\ \a \b \f \n \r \t \v
> \XYZ (where X, Y, and Z are octal digits, X <= 3, and
> at least one of the digits is nonzero)
Just to let you know, I am slowly converting apply.c to accept
this format, and also diff.c to produce this. I did not
personally like the missing double quotes around what I did
anyway, although it was easier to code.
next prev parent reply other threads:[~2005-10-14 6:59 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 19:35 [RFC] embedded TAB and LF in pathnames Junio C Hamano
2005-10-07 23:29 ` Alex Riesen
2005-10-07 23:44 ` Junio C Hamano
2005-10-08 6:45 ` Alex Riesen
2005-10-08 9:10 ` Junio C Hamano
2005-10-08 13:30 ` [PATCH] Try URI quoting for " Robert Fitzsimons
2005-10-08 18:30 ` Junio C Hamano
2005-10-08 20:19 ` Junio C Hamano
2005-10-11 6:20 ` Paul Eggert
2005-10-11 7:37 ` Junio C Hamano
2005-10-11 15:17 ` Linus Torvalds
2005-10-11 18:03 ` Paul Eggert
2005-10-11 18:37 ` Linus Torvalds
2005-10-11 19:42 ` Paul Eggert
2005-10-11 20:56 ` Linus Torvalds
2005-10-12 6:51 ` Paul Eggert
2005-10-12 14:59 ` Linus Torvalds
2005-10-12 19:07 ` Daniel Barkalow
2005-10-12 19:52 ` Linus Torvalds
2005-10-12 20:21 ` H. Peter Anvin
[not found] ` <87vf02qy79.fsf@penguin.cs.ucla.edu>
2005-10-12 21:02 ` Junio C Hamano
2005-10-12 21:05 ` Linus Torvalds
2005-10-12 21:09 ` H. Peter Anvin
2005-10-12 21:15 ` Johannes Schindelin
2005-10-12 21:33 ` Junio C Hamano
2005-10-14 0:57 ` Paul Eggert
2005-10-14 5:43 ` Linus Torvalds
2005-10-12 21:24 ` Linus Torvalds
2005-10-14 0:16 ` Paul Eggert
2005-10-14 5:20 ` Linus Torvalds
2005-10-14 17:18 ` H. Peter Anvin
2005-10-14 6:59 ` Junio C Hamano [this message]
2005-10-09 10:42 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vll0wvb2a.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=eggert@CS.UCLA.EDU \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).