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

visualizing Git's Git repo

From
Joshua Haberman <joshua@reverberate.org>
Date
May 26, 2008, 20:47 UTC
Message-ID
<CA563F5A-5E12-42F7-BDFD-04FE3A882028@reverberate.org>

I'm a casual Git user. One thing that's been troubling me about Git is that when I look at Git's own Git repository, the revision history is not at all easy to understand. I like to view my own Git repositories with:

$ gitk --all --date-order

When I run this command, what I'm really asking is "give me a visual summary of what's up with my project lately." But with Git's repository, there are far too many branches and merges for this view to make any kind of visual sense.

So my questions are:
1. what do you all do to get a high-level view of what's going on with  
Git development?  do you use gitk?  if so, what options?
2. as a project, why don't you rebase when merging long-running  
branches into master?  For example, take commit 7e83003029 from May 25  
which merged a branch that was based at 4b172de81 from May 14.  Why  
not rebase this to May 25 as part of the merge?  When you don't do  
this (ie. in the status quo) 'gitk --date-order' for the Git  
repository has >10 parallel branches most of the time, which makes it  
impossible to follow visually.

I'm sure you have reasons for doing things the way you do, I just want to hear what they are. And sorry if this is a FAQ -- feel free to point me at any documentation that explains this.

Josh
Next: Eric Hanchrow
Message 1 of 9 in “visualizing Git's Git repo”
  1. Joshua HabermanMay 26, 2008
  2. Eric HanchrowMay 26, 2008
  3. Joshua HabermanMay 26, 2008
  4. Shawn O. PearceMay 26, 2008
  5. Björn SteinbrinkMay 27, 2008
  6. Joshua HabermanMay 27, 2008
  7. Jeff KingMay 27, 2008
  8. Linus TorvaldsMay 28, 2008
  9. Jakub NarebskiMay 28, 2008

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.