From: "Marco Costalba" <mcostalba@gmail.com>
To: "Nanako Shiraishi" <nanako3@bluebottle.com>
Cc: GIT <git@vger.kernel.org>
Subject: Re: qgit: Annotate hundreds of files at terrific speed ;-)
Date: Mon, 25 Jun 2007 13:20:48 +0200 [thread overview]
Message-ID: <e5bfff550706250420s603e36eds9a2bcbb339aac80e@mail.gmail.com> (raw)
In-Reply-To: <200706250638.l5P6crkS026564@mi1.bluebottle.com>
On 6/25/07, Nanako Shiraishi <nanako3@bluebottle.com> wrote:
>
> >> Marco Costalba <mcostalba@gmail.com> wrote:
> >
> > - filtering, ie selecting with the mouse some lines and getting a
> > subset of the file history that modified at least one of that lines is
> > not possible.
>
> I often use "git blame -L'/regexp/,/regexp/'" (you can use line
> numbers there, too). Is this different from what you talk above?
>
Yes it.
Suppose you have selected file lines from 20 to 23 in revision A.
Revision history it's the following, in cronological order:
A (oldest) -> B - > C (newest)
Say that in revision B the patch removed 5 lines from 5 to 10 and
added 2 new lines instead.
Now when you jump from A to revision C you may want to see selected
the lines (-5 + 2 = -3) from 17 to 20 and no more the lines from 20 to
23 that will point to a different content.
In a general case jumping from a revision A to a revision N you have to:
- get the list of intermediate revision
- for each revision calculate deleted/ added content that is before
the selected lines range.
- for each revision calculate deleted/ added content that CROSSES the
selected range, so that if in our example revision B adds also 2 new
lines in position 21 the selection in C will not be 17 to 20 but 17 to
22! The same logic in case of deleted lines in selected range.
So to keep a "consistent" mouse selection when jumping to different
file revisions you really need to know all the annotate history in
between.
Marco
prev parent reply other threads:[~2007-06-25 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 16:35 qgit: Annotate hundreds of files at terrific speed ;-) Marco Costalba
2007-06-24 23:08 ` Shawn O. Pearce
2007-06-25 5:59 ` Marco Costalba
2007-06-25 6:35 ` Nanako Shiraishi
[not found] ` <200706250638.l5P6crkS026564@mi1.bluebottle.com>
2007-06-25 11:20 ` Marco Costalba [this message]
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=e5bfff550706250420s603e36eds9a2bcbb339aac80e@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=git@vger.kernel.org \
--cc=nanako3@bluebottle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox