Due to the chicken/egg problem, commit ids will never be up-to-date in any version controlled CFF file. The commit field is also very likely going to be removed with the next major version of CFF.
Based on the former alone, there is no good reason for cffinit to support this field. Instead of tempting users to provide a value and throw them into a maintenance nightmare, this field could be removed altogether.
thought: If the field should stay for whatever reason for now, it could be moved from the top of the page to the bottom of the page alternatively.
Due to the chicken/egg problem, commit ids will never be up-to-date in any version controlled CFF file. The
commitfield is also very likely going to be removed with the next major version of CFF.Based on the former alone, there is no good reason for cffinit to support this field. Instead of tempting users to provide a value and throw them into a maintenance nightmare, this field could be removed altogether.
thought: If the field should stay for whatever reason for now, it could be moved from the top of the page to the bottom of the page alternatively.