Dear all, we would very much like to migrate our currently CVS-managed project, the Biochemical ALgorithms Library BALL (http://www.ball-project.org) to git. Apart from the problem that our repository turned out to be horribly broken after 12 years of development -- which made conversion to git a somewhat unpleasant experience -- we would now be nearly ready to migrate. But unfortunately, we internally rely heavily on the $Id:$ - expansion of CVS, that is the ability to have a line like $Id:$ in the source file expanded to something like $Id: HINFile.C,v 1.64 2005/02/09 13:02:41 oliver Exp $ The information we want to store in the file would be something like the SHA1 of the last commit that touched that file, the date when it happened and the person who commited it. I have been thinking about trying to achieve something like this in git. >From my very limited understanding of the internals of git, I thought it should be possible to have a sed-script at the appropriate hooks that inserts the updated information into a file whenever it is affected by a commit. Do you think that this could work? And if so, would it suffice to add a pre-commit hook? I can currently see two main problems of this idea: the first is that I would expect this to do strange things when people work with a cloned or copied repository but forget to install the scripts at the correct location. This, I would be willing to ignore. The other problem I expect are lots of meaningless conflicts upon merging, since for a file that has been touched in two branches, the $Id:$ - lines will necessarily be different. Is there a way around this problem? And, more importantly, did I overlook any potentially more serious problems with such an approach? Thanks a lot, Andreas Hildebrandt - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
