un-reachable revisions from filelog

Benoit Boissinot bboissin at gmail.com
Fri Apr 30 02:20:10 CDT 2010


On Fri, Apr 30, 2010 at 8:17 AM, FUJIWARA Katsunori
<fujiwara at ascade.co.jp> wrote:
> Hi, Matt.
>
> At Wed, 28 Apr 2010 02:01:01 -0500,
> Matt Mackall wrote:
>>
>> Yup. There is no damage, just Mercurial being weird about walking
>> filelogs.
>
> This filelog-based behavir seems to be strange for ordinary usersa
> without knowledge about Mercurial internal, does not it ?
>

It does.

> But I know that making "-k"-like behavior as default for specified
> filenames would cause serious performance decreasing.

Indeed.
>
> So, how about making unification of filelog entries as configurable ?
>
>    Filelog unificiation is disabled in default, so ordinary users can
>    see all related revisions (except for removed ones) for specified
>    file.
>
>    In other hand, expert users can enable it by own configuration,
>    and specify '-k' in appropriate situations for them.
>
> This suppression would increase storage consumption a little, but I
> think that revision visibility is more important for ordinary users.

It's not as simple, we can't just duplicate the entries (it wouldn't work).
(and it would need changes to the inter-repo protocol).

Benoit


More information about the Mercurial-devel mailing list