{"thread":{"id":"20580","subject":"git-blame missing output format documentation","startedAt":"2009-08-13T12:18:11Z","lastAt":"2009-08-13T12:18:11Z","messageCount":1,"participants":["Ori Avtalion"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"120515","messageId":"4A840483.9090402@avtalion.name","threadId":"20580","inReplyTo":null,"subject":"git-blame missing output format documentation","fromName":"Ori Avtalion","fromEmail":"ori@avtalion.name","sentAt":"2009-08-13T12:18:11Z","receivedAt":"2009-08-13T12:18:11Z","isPatch":false,"sender":{"key":"ori@avtalion.name","avatar":"https://avatars.githubusercontent.com/u/28355?v=4"},"body":"Hi,\n\n\"git blame\" prefixes boundary commit tree-ish's with ^.\nThis doesn't seem to be documented in the git-blame manpage.\n\nIs it a convention used elsewhere, that it can go unmentioned?\n\nAlso, the manpage doesn't describe the format of the regualr, \nnon-porcelain, output.\nDoesn't it deserve its own section?\n\nThe only non-obvious parts to me  are the the boundary commit notation, \nmentioned above, and the filename in the second column.\n"}]}