[BUG] bogus name_version in bzr.newformat

[Robert Collins]

On Tue, 2005-10-04 at 08:14 +1000, Robert Collins wrote:
> On Mon, 2005-10-03 at 15:56 -0500, John A Meinel wrote:
> > After upgrading the bzr.newformat tree into the new format, I was
> > playing around with it, and I noticed that it seems to be updating the
> > "name_version" field even if the name did not change.
> > 
> > I realize, we may be getting rid of this field, and changing it to
> > "revision" for just the last changed version.
> > 
> > The specific file I noticed was "adoption.txt". As near as I can tell,
> > the actual name doesn't change, and neither does the parent (perhaps the
> > parent of the parent changes???) The text_sha1 doesn't ever change, and
> > the text_version seems to agree.
> > 
> > So why would the name_version be changing?
> 
> It should change if the parent or the name changes. Anyway, that field
> is nukified in my format-5 tree - could you see if it happens there ?

....
I meant 'parent ID' changes, not the state of the parent.

The idea is that any change that is done *to* the file the inventory
entry tracks results in a record being made to its weave file.

Rob

-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051004/0ded4fc2/attachment.pgp