From: Petr Baudis <pasky@suse.cz>
To: Luben Tuikov <ltuikov@yahoo.com>
Cc: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: gitweb: using quotemeta
Date: Fri, 6 Oct 2006 20:45:37 +0200 [thread overview]
Message-ID: <20061006184537.GU20017@pasky.or.cz> (raw)
In-Reply-To: <20061006182409.87381.qmail@web31812.mail.mud.yahoo.com> <20061006182105.17519.qmail@web31806.mail.mud.yahoo.com>
Dear diary, on Fri, Oct 06, 2006 at 08:21:05PM CEST, I got a letter
where Luben Tuikov <ltuikov@yahoo.com> said that...
> > According to RFC2183, the filename is a value. According to RFC2045, a
> > value is either a token (uninteresting) or a quoted-string. According to
> > RFC822:
> >
> > quoted-string = <"> *(qtext/quoted-pair) <">; Regular qtext or
> > ; quoted chars.
> >
> > qtext = <any CHAR excepting <">, ; => may be folded
> > "\" & CR, and including
> > linear-white-space>
> >
> > quoted-pair = "\" CHAR ; may quote any char
> >
> > So what we emit is completely correct.
>
> (Your quotations do not seem correct according to
> ftp://ftp.rfc-editor.org/in-notes/rfc2045.txt !)
Wow, you caused my GNOME at work to do something totally horrible after
me clicking on that link... ;-)
I'm not sure how is RFC2045 relevant - this is from RFC822, RFC2045 does
not define those non-terminals.
> Petr, I agree with your that what we emit is "completely correct".
>
> But is is _mangled_. I.e. why mangle the filename from "a.b" to
> "a\.b" ? Indeed the latter _is_ qtext but it is not the original name
> given to the file.
..snip..
> Sorry, I ment to say that the latter doesn't appear to be qtext.
>
> Bottomline is that quotemeta does not convert into qtext, and as thus
> should never have been used.
It's a moot point now, but I don't see that - inside qtext, any
character can be quoted, so what we do is technically ok.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
next prev parent reply other threads:[~2006-10-06 18:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 21:15 gitweb: using quotemeta Luben Tuikov
2006-09-28 23:18 ` Junio C Hamano
2006-09-28 23:27 ` Luben Tuikov
2006-10-02 0:28 ` Jakub Narebski
2006-10-02 20:12 ` Luben Tuikov
2006-10-02 20:50 ` Jakub Narebski
2006-10-03 6:30 ` Junio C Hamano
2006-10-06 12:38 ` Jakub Narebski
2006-10-07 5:08 ` Junio C Hamano
2006-10-07 9:23 ` Jakub Narebski
2006-10-07 17:41 ` Luben Tuikov
2006-10-11 9:48 ` Jakub Narebski
2006-10-06 13:50 ` Petr Baudis
2006-10-06 18:21 ` Luben Tuikov
2006-10-06 18:45 ` Petr Baudis [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-06 18:24 Luben Tuikov
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=20061006184537.GU20017@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=ltuikov@yahoo.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 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).