valis for bazaar-ng

[Tez Kamihira]

Hi Martin,

On Wed, 6 Jul 2005 11:30:09 +1000, Martin Pool <mbp at sourcefrog.net> said:
> I'm curious - how do you decide what deleted lines to include?

Everything. Every line that occurrs in the whole history is recorded.

> If you showed every
> deleted line for the whole history of the file it seems like it would
> be very crowded.

Yes. very crowded. So practically, some data reducing operation would
be needed. For example, "Remove all the information less than revision
N".  valis doesn't have such kind of operation yet, but it's not big deal.

> I know ClearCase can annotate deletions too

I didn't know that. I'll check it later.

> 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.

I don't know "weave format" at all. If there exists some introductory
document about it, I'd be happy. BTW I couldn't find "bzrlib/weave.py"
in your line. Does it really exist ?

> 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?

First time, yes, it's slow. I actually tried to cache your total line
of history yesterday.  I didn't measure strict cumulative time, but it
seemed to take about a few hours.  Except the initial generation, all
it has to do is to culculate delta information only, so they don't
take so much time any more.

> Does it track merged-in lines in Arch?

No. Only main line (trunk line ?) information can be cached. If bzr
handles every parent on an equal basis, I'd meet some difficuly to
implement it. I met the same situation when I tried to cache git
archive by the same way, because I heared that they can also have
multiple ancestors.

Cheers,


       - Tez