{"thread":{"id":"2089","subject":"cg-prev and cg-next","startedAt":"2005-10-13T14:38:52Z","lastAt":"2005-10-13T14:38:52Z","messageCount":1,"participants":["Zack Brown"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"10064","messageId":"20051013143852.GA5057@tumblerings.org","threadId":"2089","inReplyTo":null,"subject":"cg-prev and cg-next","fromName":"Zack Brown","fromEmail":"zbrown@tumblerings.org","sentAt":"2005-10-13T14:38:52Z","receivedAt":"2005-10-13T14:38:52Z","isPatch":false,"sender":{"key":"zbrown@tumblerings.org","avatar":null},"body":"Hi folks,\n\nSometimes I just want to surf through a project's history, getting a sense of\nwhere I was over time. So I wrote these short scripts to let me do that easily:\n\ncg-prev:\n\n    cg-seek `cg-log | grep \"^commit \" | head -n 2 | tail -n 1 | cut -d ' ' -f 2`\n\n\ncg-next:\n\n    CURRENT=`cg-log | grep \"^commit \" | head -n 1`       \n    cg-seek > /dev/null\n    cg-seek `cg-log | grep \"^commit \" | grep -B 1 \"^$CURRENT\" | head -n 1 | cut -d ' ' -f 2`\n\nEven better, I guess would be to be able to do something like this:\n\n$ cg-seek next\n$ cg-seek prev\n\nand have it do the right thing.\n\nBe well,\nZack\n\n-- \nZack Brown\n"}]}