On Mon, Feb 4, 2019 at 9:15 PM brian m. carlson <sandals@xxxxxxxxxxxxxxxxxxxx> wrote: > > On Mon, Feb 04, 2019 at 09:00:42PM -0500, Larry Martell wrote: > > Thanks for the reply. Any suggestions on how to achieve what I want to do? > > > > The use case is that we want to have a file that is part of the > > install that has certain info (commit id, date of commit, commit > > message, etc.). and we'd like that to be generated automatically. > > If you want to generate a file, you can certainly do that in the > post-commit hook or using a Makefile target. You just can't check it > into the repo. Lots of projects do this as part of their build process. > > An example of what you could do is "git log --pretty='tformat:%H%n%B' HEAD". > That will print the commit hash and commit message to standard output > for each commit. If you want just one commit, you can use "-1". Yeah, but I want it part of the repo so it makes it to the target system.
