Re: [Lxr-dev] Tag "head" in its timeline (was: /bin/true as a zombie)

[<pe...@kl...>]

Jan-Benedict Glaw <jb...@lu...> writes:

> This leads me to some question: how does genxref react on the fact
> that "head" may be something different each time it is called? For
> example I could now run a genxref on the current linux kernel, and
> I could do this 2 weeks later again. The first "head" would
> mean all those revisions as of the older kernel's version, the
> second "head" would be a more recent kernel. Any conflicts there?

Shouldn't be.  In the process of indexing (in Tagger.pm), the pathname
and symbol ('head') is looked up to find the actual revision of the
file (like '1.4').  The filename and revision is a key in the files
table in the database.  As the revision associated with the 'head' is
changed, so will the file-id in the database.  The file-id determines
if lxr thinks the file has been indexed before or not.

...Peder...
-- 
Cogito ergo panta rei.