{"thread":{"id":"10214","subject":"public repository","startedAt":"2007-10-09T13:04:00Z","lastAt":"2007-10-09T13:04:00Z","messageCount":1,"participants":["Pierre Habouzit"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"55272","messageId":"20071009130400.GA27301@artemis.corp","threadId":"10214","inReplyTo":null,"subject":"public repository","fromName":"Pierre Habouzit","fromEmail":"madcoder@debian.org","sentAt":"2007-10-09T13:04:00Z","receivedAt":"2007-10-09T13:04:00Z","isPatch":false,"sender":{"key":"madcoder@debian.org","avatar":"https://avatars.githubusercontent.com/u/44708?v=4"},"body":"  Under popular demand^W^W^Wbecause Jonas asked for my parse_options\nwork, I've put my git topic branches on a public repository on\ngit://git.madism.org/git.git.\n\n  master/next are my known positions of master and next at the time I\npushed last. ph/* are topic branches I work on, they should be either\nbsaed on master or next (hence are rebased until merged into git.git or\ndropped).\n\n  Right now, there is ph/strbuf with the 1+2 series that generated this\nheated discussion before. There is also ph/parseopt: a 10+ series\nfeaturing krh parse_options, with some rework on my end to support more\nfeatures, and I migrate a dozen of builtins to use them (in this topic\nbranch, `git rm -rf ...` works !)\n\nCheers,\n-- \n·O·  Pierre Habouzit\n··O                                                madcoder@debian.org\nOOO                                                http://www.madism.org\n"}]}