{"thread":{"id":"55035","subject":"gitk and --no-walk","startedAt":"2021-01-23T15:01:24Z","lastAt":"2021-01-23T15:01:24Z","messageCount":1,"participants":["Mikko Rantalainen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"415059","messageId":"00b30f2d-44bb-43b9-c852-45a1d9ed4346@peda.net","threadId":"55035","inReplyTo":null,"subject":"gitk and --no-walk","fromName":"Mikko Rantalainen","fromEmail":"mikko.rantalainen@peda.net","sentAt":"2021-01-23T14:53:20Z","receivedAt":"2021-01-23T15:01:24Z","isPatch":false,"sender":{"key":"mikko.rantalainen@peda.net","avatar":"https://gravatar.com/avatar/e2d770957fa98e434c238272a8ee24c02ab5766ad140c18b9591045c0a49be58?d=mp&s=160"},"body":"Dear Sirs,\n\nI asked a question about how to make gitk behave like git log --no-walk\nat https://stackoverflow.com/q/65848193/334451 and found out that gitk\nimplementation currently simply ignores --no-walk.\n\nAccording to comment near the actual code in gitk says\n\n> proc parseviewargs {n arglist} {\n> ...\n> ... \"--no-walk\" ...\n>   # These cause our parsing of git log's output to fail, or else\n>   # they're options we want to set ourselves, so ignore them.\n\nHowever, if I remove the \"--no-walk\" from that list and e.g. try to run\nfollowing command line with Linux kernel repo\n\ngitk --no-walk 7a223e06b b5de3c502 f05badde4 6ec4bae1 1b937e8f 444fe991\n\neverything seems to work just fine and I get the expected output.\nWithout modifying the gitk source code gitk just renders whole git repo\nwhich takes A LOT of time for something as complex as linux kernel.\n\nNote that I intentionally mixed the order of commit ids in the example\nabove to test that the history is still rendered correctly.\n\nIs there a reason to keep ignoring the --no-walk flag anymore?\n\n(Tested with git version 2.17.1.)\n\n-- \nBest regards,\nMikko\n"}]}