> > I would actually recommend you take a look at -L option from blame. What > I use most often and find very handy myself is this pattern: > > blame -L '/^void some_function()/,/^}/' -- path > > as I do not have to count the line numbers. I have look at that options and I find it is very convenient and line-level browser will adopt that line syntax, too. > There also was a discussion on allowing more than one -L to blame, which I > think is applicable to this feature. Check the list archive for the past > few months. I think it is rationale for 'git blame' to allow more than one -L to let the users see more than one block of code. But for a tool which used to explore history, I think the user almost focus on one thread of history. If the history split on some point, we should ask user for choose one to go on. So, I think the line-level browser need not to support such a thing. :) Regards! Bo -- 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