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

Re: log --graph: extra space with --pretty=oneline

From
TLTeemu Likonen <tlikonen@iki.fi>
Date
May 29, 2008, 10:25 UTC
Message-ID
<20080529102549.GA11074@mithlond.arda.local>
In-Reply-To
<20080529085752.GA31865@adamsimpkins.net>
Adam Simpkins wrote (2008-05-29 01:57 -0700):
> What is everyone's preference between the 3 options?  Personally, I'm
> leaning towards Option 2.

I prefer the option 2 too. To me it never looks too ugly whereas the other two have some broken line or buggy-ish cases.

Damn, this log --graph is so nice feature. I like it more than gitk, regardless of the fact that I have two monitors and could easily have gitk open and visible all the time.

Previous: Adam SimpkinsNext: Adam Simpkins
Message 6 of 12 in “log --graph: extra space with --pretty=oneline”
  1. Teemu LikonenMay 28, 2008
  2. Wincent ColaiutaMay 28, 2008
  3. Adam SimpkinsMay 29, 2008
  4. graph API: improve output for merge commits (option 1)Adam Simpkins, May 29, 2008
  5. graph API: improve output for merge commits (option 2)Adam Simpkins, May 29, 2008
  6. Teemu LikonenMay 29, 2008
  7. 0/2 graph API: improve printing of mergesAdam Simpkins, Jun 1, 2008
  8. 1/2 graph API: improve display of merge commitsAdam Simpkins, Jun 1, 2008
  9. 2/2 graph API: avoid printing unnecessary padding before some octopus mergesAdam Simpkins, Jun 1, 2008
  10. Junio C HamanoJun 1, 2008
  11. Adam SimpkinsJun 2, 2008
  12. Junio C HamanoJun 2, 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.