From: Ryan Anderson <ryan@michonline.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add git-annotate - a tool for annotating files with the revision and person that created each line in the file.
Date: Wed, 8 Feb 2006 16:07:57 -0500 [thread overview]
Message-ID: <20060208210756.GA9490@mythryan2.michonline.com> (raw)
In-Reply-To: <7vd5hxpr2d.fsf@assigned-by-dhcp.cox.net>
On Wed, Feb 08, 2006 at 11:51:22AM -0800, Junio C Hamano wrote:
> Ryan Anderson <ryan@michonline.com> writes:
>
> > Signed-off-by: Ryan Anderson <ryan@michonline.com>
> >
> > ---
> >
> > I think this version is mostly ready to go.
> >
> > Junio, the post you pointed me at was very helpful (once I got around to
> > listening to it), but the code it links to is missing - if that's a
> > better partial implementation than this, can you ressurrect it
> > somewhere? I'd be happy to reintegrate it together.
>
> I still have it, but the reason why I withdrew circulating it
> was because I found that on some inputs it did not work
> correctly as intended. Not that the algorithm was necessarily
> broken but the implementation certainly was.
>
> Unlike yours mine reads and interprets diff output to find which
> lines are common and which lines are added, and I think the diff
> interpretation logic has various corner cases wrong. I did
> combine-diff.c diff interpreter without looking at my
> 'git-blame', so I do not remember where I got it wrong,
> though...
I tried that approach at first, and it was much much more confusing to
try to keep track of. The problem Linus found (that of a missing
"all_lines_claimed()") was related to that code. This implementation is
simple, though it has to have some problems with guessing at duplicated
lines incorrectly.
> It's been a while since I looked at it the last time so it may
> not even work with the current git, but here it is..
I'll take a look through this in greater detail later, hopefully your
approach can be applied. Diff-analyzing is apparently tricky.
--
Ryan Anderson
sometimes Pug Majere
next prev parent reply other threads:[~2006-02-08 21:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 14:52 [PATCH] Add git-annotate - a tool for annotating files with the revision and person that created each line in the file Ryan Anderson
2006-02-08 15:09 ` Peter Eriksen
2006-02-08 16:05 ` Johannes Schindelin
2006-02-08 16:35 ` Franck Bui-Huu
2006-02-08 17:45 ` Johannes Schindelin
2006-02-08 19:19 ` Junio C Hamano
2006-02-10 11:25 ` Ralf Baechle
2006-02-10 11:55 ` Andreas Ericsson
2006-02-14 10:51 ` Fredrik Kuivinen
2006-02-08 18:47 ` Randal L. Schwartz
2006-02-09 9:19 ` Andreas Ericsson
2006-02-09 9:57 ` Junio C Hamano
2006-02-09 12:04 ` Franck Bui-Huu
2006-02-09 12:47 ` Andreas Ericsson
2006-02-08 19:09 ` Linus Torvalds
2006-02-08 19:51 ` Junio C Hamano
2006-02-08 21:07 ` Ryan Anderson [this message]
2006-02-08 21:45 ` Junio C Hamano
2006-02-10 22:04 ` Ryan Anderson
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=20060208210756.GA9490@mythryan2.michonline.com \
--to=ryan@michonline.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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;
as well as URLs for NNTP newsgroup(s).