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

Re: [PATCH] gitweb: make leftmost column of blame less cluttered.

From
LTLuben Tuikov <ltuikov@yahoo.com>
Date
Oct 4, 2006, 02:48 UTC
Message-ID
<20061004024837.4462.qmail@web31808.mail.mud.yahoo.com>
In-Reply-To
<7virj0lsua.fsf@assigned-by-dhcp.cox.net>
--- Junio C Hamano <junkio@cox.net> wrote:
Show 16 quoted lines
> > I like the fact that the "data part" of blame is text, and
> > that the commit-8 is on the left, and color-chunked.  Sometimes
> > people simply _remember_ a number of commit-8's and thus the
> > layout of blame is intentional, since they can look to the left
> > and recognize a commit-8...
> 
> It is not only the initial commit.  A substantial rewrite and
> new development also has the same issue.
> 
> I think you are also contradicting yourself by saying that
> people would recognize a commit-8, and at the same time you do
> not like the chunk code that makes sure you do not get too few
> of them.  If people _do_ recognize commit-8 (I seriously doubt
> that), then wouldn't it help to make sure you have them on every
> couple-dozen lines so that the user would see the familiar one
> even when scrolled?

It is not that I don't like it. For example if we didn't have the block-per-commit-coloring, then we'd make use of this, but it seems that the block-per-commit-coloring exists for the purpose to show conglomerations of same-commit lines, thus obviating the need to repeat it (commit-8) every so many lines.

The other question is how many lines should the repeat-chunk be?

In my case I'd like to set it to infinity, since the block-per-commit-coloring gives me the same information.

The other extreme case is set it to 1, thus obviating the need to use block-per-commit-coloring.

The middle ground as it seems to me, neither infinity nor 1, is to just use the block-per-commit-coloring and use your idea of printing the commit-8 only on the leading block row with mouse-over author and date info. That's an excellent idea.*

    Luben
* I've three patches which implement your excellent idea but without
using a "stack-like" chunk, eliminating the concern of rare but present
files with 100s of 1000s of lines with only an initial commit.  Should I
post them?
Previous: Junio C HamanoNext: Jakub Narebski
Message 9 of 15 in “gitweb: make leftmost column of blame less cluttered.”
  1. gitweb: make leftmost column of blame less cluttered.Junio C Hamano, Oct 1, 2006
  2. Luben TuikovOct 2, 2006
  3. Junio C HamanoOct 3, 2006
  4. Junio C HamanoOct 3, 2006
  5. Luben TuikovOct 3, 2006
  6. Martin WaitzOct 3, 2006
  7. Luben TuikovOct 3, 2006
  8. Junio C HamanoOct 4, 2006
  9. Luben TuikovOct 4, 2006
  10. Jakub NarebskiOct 4, 2006
  11. Junio C HamanoOct 4, 2006
  12. Luben TuikovOct 4, 2006
  13. Junio C HamanoOct 5, 2006
  14. Luben TuikovOct 5, 2006
  15. Luben TuikovOct 3, 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.