On Sun, Mar 21, 2010 at 5:58 AM, A Large Angry SCM <gitzilla@xxxxxxxxx> wrote: > Alex Riesen wrote: >> >> On Sat, Mar 20, 2010 at 10:18, Bo Yang <struggleyb.nku@xxxxxxxxx> wrote: >>> >>> <line range> >>> Its format should be <start pos>..<end pos> or just a <line number>. >> >> You might want to reconsider the line range syntax. Exactly the same >> syntax >> is already used to specify a commit range, so reusing it may lead to >> confusion. > > I, actually, think the proposed line range syntax works because it uses the > same _range_ notation. The issue is how to differentiate the _line_ range(s) > from the _commit_ range(s); and, yes, I would like multiple ranges of each > type as well as multiple files. As what I said in previous post, I think we should adopt 'git blame' way. Use a '-L <start pos>,<end pos>' to specify the line range. It support both line number and posix regex. For multiple ranges stuff, I don't think it is very useful to support it for a history browser. Anyway, our users can only focus on one line of thread history. I am very willing to listen what is your use case for a multiple ranges? Thanks for your precious advice! 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