valis for bazaar-ng

[Martin Pool]

On  5 Jul 2005, Tez Kamihira <tez at kamihira.com> wrote:
> I've just roughly ported valis from ViewARCH to bazaar-ng as a plugin
> module. It looks like work well. valis generates a kind of line
> annotation history, but it can record not only current active lines,
> but also deleted lines. I put an output example for Makefile in
> Martin's line at the bottom of this mail.

Hi Tez,

I'm curious - how do you decide what deleted lines to include?  Only
the lines deleted in the revision of interest.  If you showed every
deleted line for the whole history of the file it seems like it would
be very crowded.

I know ClearCase can annotate deletions too and it's useful but I
can't remember how it works.

> In Martin's line, I can see "annotate3.patch" and "annotate4.patch"
> written by Aaron. If those patches have same ability as my work, I
> don't want to make another wheel, but if they handle only current
> active lines, I think my work still has some meaning and I'd like to
> sophisticate it.
> 
> I'd like to know the current status of the issue.

I am fairly keen to move to a weave format, which can inherently
produce annotations quite easily.  (See bzrlib/weave.py and try the
"weave.py annotate" command.)  Other people like John, Aaron and
Robert may not be convinced yet that this is a good idea.  If we can
adapt something from your code that shows deletions that might be very
good.

How does this perform on arch or bzr?  I assume you have to walk back
through all previous versions, or at least until every line is
accounted for, and so it could be quite slow?  Does it track merged-in
lines in Arch?

-- 
Martin