localrepo.tags()

[Matt Mackall]

On Thu, 2008-10-09 at 09:04 -0500, David Baum wrote:
> On Wed, Oct 8, 2008 at 3:13 PM, Matt Mackall <mpm at selenic.com> wrote:
>         On Wed, 2008-10-08 at 14:51 -0500, David Baum wrote:
>         > I have a question about the operation of localrepo.tags().
>          When
>         > merging two sets of nodes for a given tag, it looks the
>         history of a
>         > and b are merged together, but the losing node (either an or
>         bn) is
>         > simply discarded.  Is this an oversight, or intentional?
>         
>         It's intentional. For the purposes of the in-memory cache,
>         we're only
>         interested in the 'effective tag', ie the one that wins. For a
>         persistent cache, we'd need to store more data.
> 
> Perhaps I'm just being dense, but I don't understand why history (ah,
> bh) is merged but the top node (an, bn) isn't.

I'm afraid it would take me hours to answer that question, as I've long
since swapped out all the relevant info. If an answer exists, it should
be in the list archives or in the test suite. But it's entirely possible
you're on to something.

-- 
Mathematics is the supreme nostalgia of our time.