[Mesa-dev] Does Mesa have a policy for OpenGL token naming?

[Nicholas Miell]

When extensions get promoted into OpenGL itself, they keep the same
token names minus the _EXT or whatever postfix, which means grepping for
the tokens in the OpenGL specification will find the implementation in
the Mesa source even if it still uses the original token names from the
extension.

Unfortunately, the OpenGL spec also gratuitously renames tokens on
occasion, which means e.g. the OpenGL 4.6 compatability spec discussion
of what used to be the EXT_fog_coord extension uses a completely
different set of token names than what's found in the Mesa source.

OpenGL 1.5 renames several tokens, 2.0 does one, 3.0 does a few, 3.2
does one, 4.1 does one, 4.2 has a Changed Tokens section that is empty,
4.3 does one, and 4.4 fixes the 4.2 Changed Tokens section to list a few
but does none for itself. The 4.2 changes are particularly weird because
they introduce new renamed tokens for some contexts but also retain the
old tokens for other contexts.

Does Mesa have a policy of which version of the tokens should be used in
the source?