Dear Kim Phillips,
In message 20100505160607.99edd83d.kim.phillips@freescale.com you wrote:
How would you try such identification?
it appears that the granularity of CHANGELOG updates is equal to that of VERSION, PATCHLEVEL, and EXTRAVERSION assignments in the root Makefile; so presumably one can refer to those instead.
This doesn't workl reliably. Too often companies insert their own version information there, which sometimes is completely unrelated to what we use.
For exact per-export granularity, one can do something like this:
cd u-boot echo '$Format:%H$' > snapshot.commit git add snapshot.commit && git commit -m 'add snapshot.commit file' echo 'snapshot.commit' > .git/info/attributes git archive --format=tar --prefix=${PREFIX}/ <commit> ...
...the resultant tarball's snapshot.commit file will contain the value of the sha id representing commit <commit>.
for more info, see the gitattributes manpage and the list of placeholders in the PRETTY FORMATS section of the git log manpage.
Ah! That's interesting. Another git feature I didn't know yet.
/me is reading the documentation.
Thanks a lot for this interesting tip!
Best regards,
Wolfgang Denk