>>>>> On Mon, 27 Feb 2017, Mike Gilbert wrote:

>> d) Should git expansion of $Id$ be enabled (i.e., ident in git
>> attributes)?

> If $Id$ is to be kept, I think point "d" needs further clarification:
> in what contexts should ident expansion be enabled?

> At rsync generation time?

> In the development repo? (via .gitattributes).

> Enabling expansion in some places but not others may cause some issues
> that would necessitate further work to prevent "$Id: xxxxxxx $"
> strings from being committed in the development repo accidentally.
> This might mean a repoman check and/or a git hook.

Right, there are many paths to insanity there. That's why we should get
rid of the whole thing altogether.

A content tracker should faithfully keep track of the files committed,
but not modify their contents. Even CVS didn't reduce $Id: something$
to $Id$, but kept the original version in the repository [1].

Ulrich

[1] http://cvsman.com/cvs-1.12.12/cvs_99.php#SEC99