{"thread":{"id":"1045","subject":"gitk and duplicate commits","startedAt":"2005-06-29T15:55:23Z","lastAt":"2005-06-29T15:55:23Z","messageCount":1,"participants":["Sven Verdoolaege"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"5415","messageId":"20050629155523.GS5992MdfPADPa@garage.linux.student.kuleuven.ac.be","threadId":"1045","inReplyTo":null,"subject":"gitk and duplicate commits","fromName":"Sven Verdoolaege","fromEmail":"skimo@kotnet.org","sentAt":"2005-06-29T15:55:23Z","receivedAt":"2005-06-29T15:55:23Z","isPatch":false,"sender":{"key":"skimo@kotnet.org","avatar":null},"body":"If I pass in the same commit multiple times (possibly\nunder different names) to gitk,\nit will echo the warning from git-rev-list\n(sort_list_in_merge_order: duplicate commit 82e3583b9426c193659a4c1315d6a3b3cee11dce ignored)\nand then simply stop.\n\nSurely this can be handled more gracefully.\n\nNote that I do want to be able to pass the same commit\nmultiple times.  At least, I don't want to check\nwhether two \"branches\" happen to refer to the same commit.\n\nskimo\n"}]}