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

Re: git log --graph --oneline issues (very small edge case)

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 20, 2014, 00:53 UTC
Message-ID
<xmqqa92jcfbg.fsf@gitster.dls.corp.google.com>
In-Reply-To
<71B93170AE5D4ED08EF12CED427299C4@black>
"Jason Pyeron" <jpyeron@pdinc.us> writes:
Show 5 quoted lines
> When a repo has multiple initial commits, the oneline graph can get borked.
>
> It will put a commit * with no parent directly above the next commit *
> with no children. This gives the false impression that the two commits
> are a sequence on a branch.
Sounds vaguely familiar.
http://thread.gmane.org/gmane.comp.version-control.git/236708/focus=239580

My preference is what I wrote after three-dash lines as "It may actually make sense ... If we did so, the output ... may look like this" there.

Previous: Jason Pyeron
Message 2 of 2 in “git log --graph --oneline issues (very small edge case)”
  1. Jason PyeronDec 19, 2014
  2. Junio C HamanoDec 20, 2014

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.