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

Re: Make "gitk" work better with dense revlists

From
Paul Mackerras <paulus@samba.org>
Date
Oct 27, 2005, 06:16 UTC
Message-ID
<17248.28857.90315.543669@cargo.ozlabs.ibm.com>
In-Reply-To
<Pine.LNX.4.64.0510251253110.10477@g5.osdl.org>
Linus Torvalds writes:
> So this makes gitk just show the diff of _that_ commit.
Committed and pushed out, but ...
> Also, having now tested the previous "handle root commit in the 
> TREECHANGED" logic a bit more, I think it's (a) stable and (b) the right 
> thing to do. Sign me off on that one too.
What is that about?

I'm hoping to get back to gitk hacking RSN - I've been going flat out on the ppc32/ppc64 merge. Thanks for doing the --dense thing; I was thinking about doing something like that inside gitk but doing it in git-rev-list is better. It does mean that I now want to be able to get gitk to contract the view to just a given set of files or directories and then expand back to the whole tree view, which means running git-rev-list multiple times, which gitk can't do at the moment...

Paul.
Previous: Linus TorvaldsNext: Junio C Hamano
Message 2 of 5 in “Make "gitk" work better with dense revlists”
  1. Linus TorvaldsOct 25, 2005
  2. Paul MackerrasOct 27, 2005
  3. Junio C HamanoOct 27, 2005
  4. Linus TorvaldsOct 27, 2005
  5. Sven VerdoolaegeOct 27, 2005

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.