Thomas Rast <trast@xxxxxxxxxxx> writes: >> Even though I am moving from builtin/blame.c to line-log.c? I would >> otherwise have to call from a rather lib-ish file into a "front > > You haven't sent any reply to this. Does that mean you agree? Would > you prefer the shared file to be named something like line-range.c? The latter, or if you do not want a churn, not moving it out of blame.c at all. Because "log -L" does not play well with other patch options, from the end-user's perspective, even though may does not have cmd_logL() entry point, I do not think line-log.c is any more library-ish than cmd_log() or cmd_blame(). -- 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