Seeking information about lightweight copying/renaming

[Paul Malmsten]

>
> Right, okay. To be honest, I was hoping to do this work "myself",
> although like I said I have so far only managed to rebase the patch
> queue, combine a few patches, get an overview, plan the wire stuff and
> push a small patch out.
>
>
I have no problem if you want to take point on the project; I'm just trying
to find something interesting to do this summer. When I free up in roughly a
month, would there be any way for me to assist you? If you feel that you've
got this feature covered, I can work on something else.


> > That's true, although some of the current tests md5sum the revlogs, so if
> > they are affected by a lightweight copy feature, they will need to be
> > updated. Also, my thought was to add one or more tests which verify
> correct
> > creation/reading of lightweight copy revlogs in isolation, perhaps with a
> > similar approach.
>
> Yes... the latter sounds more like unit tests, which we don't have many
> of. But that's not a reason for not writing them :). As for the hashes,
> they will stay the same, ensuring full compatability between the same
> repo running with or without lwcopy.
>
>
Are you perhaps referring to Mercurial's internal changeset hashes? I
understand that those won't change, but the functional tests for the local
copy feature simply md5sum the revlog files to verify that they were created
correctly. Since the file format will change, won't the tests need
updating?

Thanks,
~Paul Malmsten
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial/attachments/20100407/14f8f33c/attachment.htm>