"Robin H. Johnson" <robbat2@xxxxxxxxxx> writes: > This is perhaps a reasonable wording of my requirement. > "Files from from the VCS should contain a stable machine-usable > identifier that is unique for that revision of the file, without > post-processing to insert the identifier." But what is the "revision of the file"? The blob ID is just a hash of the contents, and doesn't say anything about where in the history of the project it appears. It will usually appear in many "project revisions", i.e. commits. If you want to mark the "revision" of a file, the only sensible thing is to use the commit ID, which will give you all the problems described in this thread. -- David Kågedal - 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