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 26, 2008, 23:42 UTC
Message-ID
<loom.20080526T233903-825@post.gmane.org>
In-Reply-To
<87ve104qoz.fsf@offby1.atm01.sea.blarg.net>
Eric Hanchrow <offby1 <at> blarg.net> writes:
Show 5 quoted lines
> 
> You might not know -- I didn't until five minutes ago -- that you can
> omit entire branches, like this:
> 
>         $ gitk --all  ^refs/remotes/origin/man ^refs/remotes/origin/html

Thanks for the tip -- I had tried the converse, which is to only include master, but both this and your strategy still leave at least 10 concurrent branches at almost any point in time.

Josh
Previous: Eric HanchrowNext: Shawn O. Pearce
Message 3 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.