git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: gitweb: using quotemeta

From
Jakub Narebski <jnareb@gmail.com>
Date
Oct 2, 2006, 00:28 UTC
Message-ID
<efpme9$o13$1@sea.gmane.org>
In-Reply-To
<20060928232752.99373.qmail@web31804.mail.mud.yahoo.com>
Luben Tuikov wrote:
Show 15 quoted lines
> --- Junio C Hamano <junkio@cox.net> wrote:
>> 
>> Ouch, that was a sloppy planning and coding, and sloppier
>> reviewing.  Sorry.
>> 
>> What is the right quoting there?  Just quoting double-quotes?
> 
> I'm not sure.  What undesired character could we have in $filename
> of a snapshot?  The commit ab41dfbfd4f message gives this
> justification: "Just in case filename contains end of line character."
> 
> It looks like $filename is constructed by well defined strings:
> basename($project), $hash and $suffix all of which should be ok.
> 
> I'd say we don't need quotemeta for $filename of snapshot.

But we do need quoting for blob_plain and perhaps blobdiff_plain views, although not quotemeta, but perhaps the reverse of unescape, i.e. quote '"', EOLN (end of line) and perhaps also TAB.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Previous: Luben TuikovNext: Luben Tuikov
Message 4 of 14 in “gitweb: using quotemeta”
  1. Luben TuikovSep 28, 2006
  2. Junio C HamanoSep 28, 2006
  3. Luben TuikovSep 28, 2006
  4. Jakub NarebskiOct 2, 2006
  5. Luben TuikovOct 2, 2006
  6. Jakub NarebskiOct 2, 2006
  7. Junio C HamanoOct 3, 2006
  8. Jakub NarebskiOct 6, 2006
  9. Junio C HamanoOct 7, 2006
  10. Jakub NarebskiOct 7, 2006
  11. Luben TuikovOct 7, 2006
  12. Jakub NarebskiOct 11, 2006
  13. Petr BaudisOct 6, 2006
  14. Luben TuikovOct 6, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.