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

gitk and duplicate commits

From
SVSven Verdoolaege <skimo@kotnet.org>
Date
Jun 29, 2005, 15:55 UTC
Message-ID
<20050629155523.GS5992MdfPADPa@garage.linux.student.kuleuven.ac.be>

If I pass in the same commit multiple times (possibly under different names) to gitk, it will echo the warning from git-rev-list (sort_list_in_merge_order: duplicate commit 82e3583b9426c193659a4c1315d6a3b3cee11dce ignored) and then simply stop.

Surely this can be handled more gracefully.

Note that I do want to be able to pass the same commit multiple times. At least, I don't want to check whether two "branches" happen to refer to the same commit.

skimo
Message 1 of 1 in “gitk and duplicate commits”
  1. Sven VerdoolaegeJun 29, 2005

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.