{"thread":{"id":"2124","subject":"Scribblings for a cogito/git tutorial","startedAt":"2005-10-17T15:04:54Z","lastAt":"2005-10-21T20:51:29Z","messageCount":3,"participants":["Horst von Brand","David Whistler","Petr Baudis"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"10177","messageId":"200510171504.j9HF4stb006164@laptop11.inf.utfsm.cl","threadId":"2124","inReplyTo":null,"subject":"Scribblings for a cogito/git tutorial","fromName":"Horst von Brand","fromEmail":"vonbrand@inf.utfsm.cl","sentAt":"2005-10-17T15:04:54Z","receivedAt":"2005-10-17T15:04:54Z","isPatch":false,"sender":{"key":"vonbrand@inf.utfsm.cl","avatar":"https://avatars.githubusercontent.com/u/211384?v=4"},"body":"I've also been asked around here for a cogito+git tutorial, to that end\nI've made up a script that simulates several developers interacting.\nHacking around is simulated by patching, ed(1) scripts (merges don't turn\nout the same diff every time), and plain copying new files in. I've set up\na GPG key with an empty passphrase (comment is \"Experimental\") to have\nsigned tags, etc. in a convenient manner. The idea is to create interesting\nhistories (for browsing) and show off the commands in a compact way. If\nonly there was a convenient way to run a strech of the (bash) script, look\nat the results, and then resume...\n\nComments, suggestions, patches are welcome! \n\nRepository of the script and supporting files is at\n<http://pincoya.inf.utfsm.cl/Script.git>\n-- \nDr. Horst H. von Brand                   User #22616 counter.li.org\nDepartamento de Informatica                     Fono: +56 32 654431\nUniversidad Tecnica Federico Santa Maria              +56 32 654239\nCasilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513\n"},{"id":"10195","messageId":"loom.20051018T042052-760@post.gmane.org","threadId":"2124","inReplyTo":"200510171504.j9HF4stb006164@laptop11.inf.utfsm.cl","subject":"Re: Scribblings for a cogito/git tutorial","fromName":"David Whistler","fromEmail":"dwhistler@gmail.com","sentAt":"2005-10-18T02:28:19Z","receivedAt":"2005-10-18T02:28:19Z","isPatch":false,"sender":{"key":"dwhistler@gmail.com","avatar":null},"body":"Horst von Brand <vonbrand <at> inf.utfsm.cl> writes:\n\n> \n> Comments, suggestions, patches are welcome! \n> \n> Repository of the script and supporting files is at\n> <http://pincoya.inf.utfsm.cl/Script.git>\n\n\nI can't read it.  Seems to be a recursive trick.\n\nOr did you mean to do that?\n\n-d\n"},{"id":"10439","messageId":"20051021205129.GI30889@pasky.or.cz","threadId":"2124","inReplyTo":"200510171504.j9HF4stb006164@laptop11.inf.utfsm.cl","subject":"Re: Scribblings for a cogito/git tutorial","fromName":"Petr Baudis","fromEmail":"pasky@suse.cz","sentAt":"2005-10-21T20:51:29Z","receivedAt":"2005-10-21T20:51:29Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Mon, Oct 17, 2005 at 05:04:54PM CEST, I got a letter\nwhere Horst von Brand <vonbrand@inf.utfsm.cl> told me that...\n> I've also been asked around here for a cogito+git tutorial, to that end\n> I've made up a script that simulates several developers interacting.\n> Hacking around is simulated by patching, ed(1) scripts (merges don't turn\n> out the same diff every time), and plain copying new files in. I've set up\n> a GPG key with an empty passphrase (comment is \"Experimental\") to have\n> signed tags, etc. in a convenient manner. The idea is to create interesting\n> histories (for browsing) and show off the commands in a compact way. If\n> only there was a convenient way to run a strech of the (bash) script, look\n> at the results, and then resume...\n> \n> Comments, suggestions, patches are welcome! \n> \n> Repository of the script and supporting files is at\n> <http://pincoya.inf.utfsm.cl/Script.git>\n\nThanks, it's very nice! If you don't mind (actually, is it / can it be GPL?),\nI added it to Cogito as Documentation/tutorial-script/ .\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nVI has two modes: the one in which it beeps and the one in which\nit doesn't.\n"}]}