From: Bo Yang <struggleyb.nku@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: gitzilla@gmail.com, Alex Riesen <raa.lkml@gmail.com>,
git@vger.kernel.org
Subject: Re: GSoC draft proposal: Line-level history browser
Date: Mon, 22 Mar 2010 12:34:26 +0800 [thread overview]
Message-ID: <41f08ee11003212134s586aa71cs23255d02f38d53d1@mail.gmail.com> (raw)
In-Reply-To: <7vfx3tvv9y.fsf@alter.siamese.dyndns.org>
> Horrible. That is not how we name things.
>
> What's wrong with bog standard:
>
> $ git log -L 10,20 master -- Documentation/git.txt
>
> which is exactly how "blame" does it?
The 'blame' way is very good if we only support one line range. But if
we want to support multiple line ranges, I don't think it is suitable
for that case. Anyway, how can I specify multi-ranges which refers to
multiple files at multiple revision and multiple line ranges using
above syntax?
Except that, I still can't convince myself that we need multiple
ranges support. Anyway, how do we display such a result to our users?
Regards!
Bo
next prev parent reply other threads:[~2010-03-22 4:39 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-20 9:18 GSoC draft proposal: Line-level history browser Bo Yang
2010-03-20 11:30 ` Johannes Schindelin
2010-03-20 13:10 ` Bo Yang
2010-03-20 13:30 ` Junio C Hamano
2010-03-21 6:03 ` Bo Yang
2010-03-20 13:36 ` Johannes Schindelin
2010-03-21 6:05 ` Bo Yang
2010-03-20 20:35 ` Alex Riesen
2010-03-20 20:57 ` Junio C Hamano
2010-03-21 6:10 ` Bo Yang
2010-03-20 21:58 ` A Large Angry SCM
2010-03-21 6:16 ` Bo Yang
2010-03-21 13:19 ` A Large Angry SCM
2010-03-22 3:48 ` Bo Yang
2010-03-22 4:24 ` Junio C Hamano
2010-03-22 4:34 ` Bo Yang [this message]
2010-03-22 5:32 ` Junio C Hamano
2010-03-22 7:31 ` Bo Yang
2010-03-22 7:41 ` Junio C Hamano
2010-03-22 7:52 ` Bo Yang
2010-03-22 8:10 ` Jonathan Nieder
2010-03-23 6:01 ` Bo Yang
2010-03-23 10:08 ` Jakub Narebski
2010-03-23 10:38 ` Bo Yang
2010-03-23 11:22 ` Jakub Narebski
2010-03-23 12:23 ` Bo Yang
2010-03-23 13:49 ` Jakub Narebski
2010-03-23 15:23 ` Bo Yang
2010-03-23 19:57 ` Jonathan Nieder
2010-03-23 21:51 ` A Large Angry SCM
2010-03-24 2:30 ` Bo Yang
2010-03-23 12:02 ` Peter Kjellerstedt
2010-03-23 18:57 ` Jonathan Nieder
2010-03-24 2:39 ` Bo Yang
2010-03-24 4:02 ` Jonathan Nieder
2010-03-22 10:39 ` Alex Riesen
2010-03-22 15:05 ` Johannes Schindelin
2010-03-22 3:52 ` Bo Yang
2010-03-22 15:48 ` Jakub Narebski
2010-03-22 18:21 ` Johannes Schindelin
2010-03-22 18:38 ` Sverre Rabbelier
2010-03-22 19:26 ` Johannes Schindelin
2010-03-22 20:21 ` Sverre Rabbelier
2010-03-22 19:24 ` Johannes Schindelin
2010-03-23 6:08 ` Bo Yang
2010-03-23 6:27 ` Bo Yang
[not found] ` <201003282120.40536.trast@student.ethz.ch>
2010-03-29 4:14 ` Bo Yang
2010-03-29 18:42 ` Thomas Rast
2010-03-30 2:52 ` Bo Yang
2010-03-30 9:07 ` Michael J Gruber
2010-03-30 9:38 ` Michael J Gruber
2010-03-30 11:10 ` Bo Yang
2010-03-30 9:10 ` Jakub Narebski
2010-03-30 11:15 ` Bo Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41f08ee11003212134s586aa71cs23255d02f38d53d1@mail.gmail.com \
--to=struggleyb.nku@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=gitzilla@gmail.com \
--cc=raa.lkml@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.