René Scharfe <rene.scharfe@xxxxxxxxxxxxxx> writes: > Hmm, even shorter would be to leave out these "==" things entirely: > > # mock-up > $ git grep -p -n markers grep.c > grep.c=746=static void clr_hit_marker(struct grep_expr *x) > grep.c:748: /* All-hit markers are meaningful only at... > grep.c=760=static int chk_hit_marker(struct grep_expr *x) > grep.c:762: /* Top level nodes have hit markers. See... > grep.c=772=int grep_buffer(struct grep_opt *opt, const ch... > grep.c:782: * We first clear hit markers from them. > > Is that still readable? Actually the above matches what I expected to see when I read your [0/6]. Is the use of '=' your invention, or does somebody's grep have this function header feature already and use '=' the same way? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html