I would recommend studying git.git's Makefile and seeing how they generate
their version file. It doesn't use a hook; it's part of the build.
--
David
On Apr 28, 2011, at 1:36 PM, Greg Moser <[email protected]> wrote:
> So in my .git/hooks folder I have a file named post-commit that looks like
> this:
>
>
> #!/bin/sh
>
> rm version.txt -i
> git describe --tags >> version.txt
>
>
> Basically the idea being that after every commit, I write the "git describe"
> to a file in my repository called version.txt. This script works fine except
> that I obviously once the file is edited, it needs to be committed. How
> should I achieve this end goal?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/git-users?hl=en.
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/git-users?hl=en.
