There is the equivalent $Header$, $Date$, $log$ of CVS in Git for C source code ?

Hello everyone. Can you tell me if the CVS equivalent $Header$, $Date$, $log$ and $Id$, exists in Git for the C source code ?

Here is this piece of code as an example:

Code:

---

/* $Header$
 * My Name      $Date$
 *
 * <Description>
 *
 * $log$
*/
static const char rcsid[] = "$Id$";

---

Yes, but no.

The problem is that git wants to compare the files, and if you change the files (by modifying the $Date$ or whatever) then it thinks there is a pending change.

In general, this information is available from the commit log, and the expectation is that should get it from there. If you want a mapping of file to checksum, create a separate file and write a script to update it as part of your release process:

1. Modify your source files. Test, debug, repeat.
2. Commit all your source files. Integration test, debug, repeat.
3. Just prior to release, use a script to dump git log, and create the filespec-to-checksum mapping file.
4. Commit that file.
5. Release.

Quote:

---

Originally Posted by aghast

Yes, but no.

The problem is that git wants to compare the files, and if you change the files (by modifying the $Date$ or whatever) then it thinks there is a pending change.

In general, this information is available from the commit log, and the expectation is that should get it from there. If you want a mapping of file to checksum, create a separate file and write a script to update it as part of your release process:

1. Modify your source files. Test, debug, repeat.
2. Commit all your source files. Integration test, debug, repeat.
3. Just prior to release, use a script to dump git log, and create the filespec-to-checksum mapping file.
4. Commit that file.
5. Release.

---

Good advice!

Thanks for the advice, but my request arises from the need to have a history of its evolution and correction for each source .c / .h file. Git gives me the information on the evolution of the whole project and not of each component file (as Subversion does).

If you want to know what happened on a per file basis, just type
git log path/to/file
It will tell you just those commits which affected that file.

Similarly for some sub-directory, like the one containing all the source.

Storing $log inside the file is so 1980's.

Quote:

---

Originally Posted by Salem

If you want to know what happened on a per file basis, just type
git log path/to/file
It will tell you just those commits which affected that file.

Similarly for some sub-directory, like the one containing all the source.

Storing $log inside the file is so 1980's.

---

This is the way I tend to do it; both work I have no idea if a corner case where one does not work exists

Code:

---

git log -- path/to/file

---

Tim S.

thanks stahta01