I plan on moving my company from CVS to Git, and some engineers want us to still use CVS keyword strings, such as $Id: $. I read all about implementing this with the ident setting .gitattributes, and I understand why this is undesirable, although perhaps for smaller source trees as well. (Our source is huge, so I think that would be impossible.)
Our engineers do not really care about the presence of the SHA1 hash file in the file. They just want to know:
- date of last modification
- committer name
- maybe commit message
It is very convenient for them to see this information in the file headers when viewing the code, and I can not argue with that.
I want to know:
Is there a way to info-stamp all step-by-step files at the moment before git commit? In other words, to run the perl command, which replaces with the $Id: $block of the desired information - on working copies of files that were committed?
This will not require any action .gitattributes. git just needed to know how to combine two such blocks of information, ideally by choosing a later one. The printed information will be just another file change in the newly created version.
I looked at this in a preliminary commit, but it seems it is designed differently - not for editing files, but only for checking them. Am I right about that?
? , , git , , .gitattributes.
//.