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

Re: visualizing Git's Git repo

From
Joshua Haberman <joshua@reverberate.org>
Date
May 27, 2008, 20:36 UTC
Message-ID
<loom.20080527T202009-498@post.gmane.org>
In-Reply-To
<CA563F5A-5E12-42F7-BDFD-04FE3A882028@reverberate.org>
Joshua Haberman <joshua <at> reverberate.org> writes:
> 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?

I get the impression from this thread that core Git developers don't make visualizing the repository a regular part of their development workflow. Is that accurate? What do you all do to keep tabs on Git development?

> 2. as a project, why don't you rebase when merging long-running  
> branches into master?

Is there really no rationale that anyone can offer for why you do things this way? I look to Git's own Git repo for best practices, and given Git's emphasis on "history hygiene" I'm certain that there are reasons for why you do things the way you do.

Josh
Previous: Björn SteinbrinkNext: Jeff King
Message 6 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.