Edmundo Carmona Antoranz <eantor...@gmail.com> writes: > So, this is a draft of what I mean by "adding tips to blame". > > Example output (sample from builtin/blame.c): > ... > 15:32 $ ./git blame --tips -L 1934,1960 builtin/blame.c > cee7f245dc: git-pickaxe: blame rewritten. > cee7f245dc builtin-pickaxe.c (Junio C Hamano 2006-10-19 > 16:00:04 -0700 1934)
This is unfortunately unreadable to guess what you wanted to achieve, not because the lines are too wide, but because they are line-wrapped. > Does it look "worthy"? And if so, would it be better to think of > something like an "aggregate" option (or something like that) that > would include the common information as tips, something like: What is the target audience? If you are trying to write a script that reads output by "git blame", you are strongly discouraged unless you are reading from "git blame --porcelain" which is more compact and has this information already IIRC.
