{"thread":{"id":"17444","subject":"border-case/general git test repository","startedAt":"2009-01-29T18:54:40Z","lastAt":"2009-01-29T18:54:40Z","messageCount":1,"participants":["Johannes Gilger"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"102489","messageId":"glsu1g$egf$1@ger.gmane.org","threadId":"17444","inReplyTo":null,"subject":"border-case/general git test repository","fromName":"Johannes Gilger","fromEmail":"heipei@hackvalue.de","sentAt":"2009-01-29T18:54:40Z","receivedAt":"2009-01-29T18:54:40Z","isPatch":false,"sender":{"key":"heipei@hackvalue.de","avatar":"https://avatars.githubusercontent.com/u/6072?v=4"},"body":"Hi,\n\npartly because of laziness, partly out of curiosity I was wondering if \nanyone had a (relatively small) test-repository lying around, that \nespecially stresses the output (not really the integrity of the data) of \ngit and all kinds of different combinations of operations.\n\nWe could really use it for GitX, as GitX parses the output of git and \neverytime we think we have found/fixed a glitch in the display we \ndiscover some new case. For example we just noticed that we didn't \ndetect file-mode changes, and after we implemented that we thought that, \nof course, a file can change its mode and content at the same time...  \nand so on ;)\n\nSo things we're looking for are things that usually don't happen that \noften (because of obscureness or because of convention respected by \npeople) but are still perfectly valid output that our/other programs \ncould trip over.\n\nGreetings,\nJojo\n\n-- \nJohannes Gilger <heipei@hackvalue.de>\nhttp://hackvalue.de/heipei/\nGPG-Key: 0x42F6DE81\nGPG-Fingerprint: BB49 F967 775E BB52 3A81  882C 58EE B178 42F6 DE81\n"}]}