[PATCH RFC] filtering: rename filters to their antonyms

Kevin Bullock kbullock+mercurial at ringworld.org
Sun Jan 13 14:30:22 CST 2013


On 13 Jan 2013, at 2:11 PM, Pierre-Yves David wrote:

> On 13 janv. 2013, at 20:48, Kevin Bullock wrote:
> 
>> # HG changeset patch
>> # User Kevin Bullock <kbullock at ringworld.org>
>> # Date 1358062756 21600
>> # Node ID 2e93234688c3921031981b1107d0769e15c81406
>> # Parent  948f495fb2302a6241787a2d5924ef328f2f4967
>> filtering: rename filters to their antonyms
>> 
>> Now that changelog filtering is in place, it's become evident that
>> naming the filters according to the set of revs _not_ included in the
>> filtered changelog is confusing. This is especially evident in the
>> collaborative branch cache scheme.
> 
> Yes, visible part of the repo are subset of each other when the set of filtered revision are superset of each other.
> 
> This change seems a good move to prevent later confusion and head blowing as we had with obsolescence marker direction.
> 
> The change seems pretty ok itself except I'm not fan of "nonvolatile". Can we find an alternative around the "Foundation" (of building) concept?

Alternatives I considered when writing this changeset late last night included "petrified", "solid" (easily confused with old phase/"liquid" terminology), "static" (perhaps the most overloaded term in computing).

Something that suggests the _reason_ these changes are unlikely to be impacted by history editing—namely, that they don't follow any mutable changes in revision number order—would be ideal, but I'm not coming up with anything at the moment.

pacem in terris / мир / शान्ति / ‎‫سَلاَم‬ / 平和
Kevin R. Bullock



More information about the Mercurial-devel mailing list