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

Re: [PATCH/RFC (take 2)] gitweb: New improved patchset view

From
Jakub Narebski <jnareb@gmail.com>
Date
Oct 30, 2006, 00:34 UTC
Message-ID
<200610300134.53668.jnareb@gmail.com>
In-Reply-To
<200610300051.37896.jnareb@gmail.com>

Few other questions, probably to be adressed in the future patches, and not added to this one.

0. git-ls-tree and git-diff-tree without -z does quote not only !isprint 
characters like LF '\n' and non-space whitespace characters like TAB 
'\t' (and of course quoting characters '\' and '"'), but for example 
also UTF-8 characters. See for example git-ls-tree output for 
gitweb/test directory. This screws somewhat idea how we should treat 
filenames which are quoted.

[BTW. How git should deal with being deployed in the environment where filesystem pathnames coding might not be UTF-8, and console (terminal) coding might be not UTF-8?]

1. Current version doesn't display empty patches (i.e. pure rename and 
mode change combinations) and doesn't provide links to them from 
difftree. This is legacy of old /usr/bin/diff using code, which did not 
generated extended diff header, which is only output for "empty 
patches". Should we change this, or leave as is?
2. Schould we change syntax highlighting of chunk header line, namely 
changing slightly syntax coloring of "in which function are we" part of 
chunk header?
3. Should we make from-range/to-range in chunk header hyperlink to the 
start of given bunch of lines in appropriate file? Or perhaps to the 
middle of the bunch of lines? Or to first changed line (omitting 
context)?
-- 
Jakub Narebski
Previous: Jakub NarebskiNext: Junio C Hamano
Message 6 of 8 in “gitweb: New improved patchset view”
  1. gitweb: New improved patchset viewJakub Narebski, Oct 29, 2006
  2. Anand KumriaOct 29, 2006
  3. Luben TuikovOct 29, 2006
  4. Luben TuikovOct 29, 2006
  5. gitweb: New improved patchset viewJakub Narebski, Oct 29, 2006
  6. Jakub NarebskiOct 30, 2006
  7. Junio C HamanoOct 30, 2006
  8. Jakub NarebskiOct 30, 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.