First, thank you for your answers! > > Very likely it isn't, but it's your choice. ;) > >> Because after having this hash one can build up all necessary info from it: > > Depending on your definition of "necessary". I'm trying to find a way to get to state where i can do $ git log <path> Or any other variants of it without introducing any non-default scripts/features/keywords and limiting keywords to one to avoid any related problem... One of my friends said that git is not working for their development model... C++ development with static linking across the board, where they need to see exactly which version of the file has got to the executable. Roughly, they are using CVS' keywords and revision numbers and a script wich matches them between two versions of the executables. I've got curious if Git can support it and how it can be done with minimal changes to workflow. > >> #finding blobs with SHA indicated in $Id$ keword >> $ git log --no-abbrev --raw --all | grep SHA-1 > > yeah. These are all starting from commit which introduced > the hash under a specific path, ending at the commit where > the path contains another SHA-1. Actually, grep "SHA-1 A" will show added path(s) only, so this is resolved > >> # little script or regexp here (don’t have it) >> $ pull out path from result >> >> # last commit for the path with all corresponding info >> $ git log -1 HEAD path >> >> So, this seems to cover most of the needs of people who would like to >> use keywords expansion, if they are not ready to forget about them… >> >> Does it make sense? > > Not much. You'll always get a long list of commits which didn't > change the damned blob. And you have absolutely no way > to find out exactly which of the commits have produced > the blob you're looking at (because you decided to do away > with the information). How is that? It seams to me that git log <path> will show only commits where <path> was changed/committed? Considering the fact that I've got the initial path from the blob, i should get the exact commit history (or last commit in my example) for the file(s) (Files if renaming occurred without content change). Thanks, Eugene -- 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