{"thread":{"id":"3302","subject":"gitk: searching on filenames?","startedAt":"2006-02-11T15:42:32Z","lastAt":"2006-02-11T15:42:32Z","messageCount":1,"participants":["walt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"15925","messageId":"Pine.LNX.4.64.0602110729450.23279@x2.ybpnyarg","threadId":"3302","inReplyTo":null,"subject":"gitk: searching on filenames?","fromName":"walt","fromEmail":"wa1ter@myrealbox.com","sentAt":"2006-02-11T15:42:32Z","receivedAt":"2006-02-11T15:42:32Z","isPatch":false,"sender":{"key":"wa1ter@myrealbox.com","avatar":null},"body":"A real example from this morning:  I noticed when pulling from\nLinus that kernel/sched.c had been updated, so I wanted to look\nat that particular commit.\n\nIf I do 'gitk kernel/sched.c' then it does what I expect.\n\nBut, if I just start gitk with no arguments and then attempt\nto search for kernel/sched.c it eventually stops with an error\nsaying \"can't find diffs for <SHA1> <SHA2>\".\n\nIs this the expected behavior?  (I have the 'Files' field\nselected in the gitk search bar.)\n\nThanks!\n"}]}