* gitk and duplicate commits
@ 2005-06-29 15:55 Sven Verdoolaege
0 siblings, 0 replies; only message in thread
From: Sven Verdoolaege @ 2005-06-29 15:55 UTC (permalink / raw
To: Paul Mackerras; +Cc: git
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-06-29 16:12 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-06-29 15:55 gitk and duplicate commits Sven Verdoolaege
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).