{"thread":{"id":"689","subject":"seek request","startedAt":"2005-05-22T07:11:06Z","lastAt":"2005-05-26T08:29:41Z","messageCount":2,"participants":["Zack Brown","Petr Baudis"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"3741","messageId":"20050522071106.GA8060@tumblerings.org","threadId":"689","inReplyTo":null,"subject":"seek request","fromName":"Zack Brown","fromEmail":"zbrown@tumblerings.org","sentAt":"2005-05-22T07:11:06Z","receivedAt":"2005-05-22T07:11:06Z","isPatch":false,"sender":{"key":"zbrown@tumblerings.org","avatar":null},"body":"Hi folks,\n\nIn Cogito, it would be nice to have a\n\ncg-seek +\n\nthat would seek to the next archive state. This way, I could start off seeking\nback to the beginning of an archive, and quickly step forward, looking at files\nas I went, to the present.\n\nA corresponding\ncg-seek -\nwould go the reverse direction, back toward the beginning of a project.\n\nI'm not sure how useful this would be for actual source code - I suspect any\nbenefit would be minimal - but the benefit for documentation and text files,\nwhere the only way to test improvements is to read them by eye, would be\nsignificant.\n\nBe well,\nZack\n\n-- \nZack Brown\n"},{"id":"3978","messageId":"20050526082941.GC22262@pasky.ji.cz","threadId":"689","inReplyTo":"20050522071106.GA8060@tumblerings.org","subject":"Re: seek request","fromName":"Petr Baudis","fromEmail":"pasky@ucw.cz","sentAt":"2005-05-26T08:29:41Z","receivedAt":"2005-05-26T08:29:41Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Sun, May 22, 2005 at 09:11:06AM CEST, I got a letter\nwhere Zack Brown <zbrown@tumblerings.org> told me that...\n> Hi folks,\n> \n> In Cogito, it would be nice to have a\n> \n> cg-seek +\n> \n> that would seek to the next archive state. This way, I could start off seeking\n> back to the beginning of an archive, and quickly step forward, looking at files\n> as I went, to the present.\n> \n> A corresponding\n> cg-seek -\n> would go the reverse direction, back toward the beginning of a project.\n> \n> I'm not sure how useful this would be for actual source code - I suspect any\n> benefit would be minimal - but the benefit for documentation and text files,\n> where the only way to test improvements is to read them by eye, would be\n> significant.\n\nWell, and what if the commit has multiple parents? Or - even much more\ninterestingly - multiple children?\n\nIf we keep applying the first parent rule, we could just traverse the\ngraph from heads/master to HEAD following this rule, and then just take\na step back to where we came from for cg-seek +. It wouldn't be exactly\ncheap, but it'd probably work.\n\nPatch welcomed. ;-)\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nC++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor\n"}]}