Hello,
with my GIT repository on Windows, I get the follwing problem when i run
git gc --aggrerssive:
$ git gc --aggressive
Counting objects: 165072, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (112141/112141), done.
Writing objects: 100% (165072/165072), done.
Total
Peter,
I would solve this in the CI (build) server. They usually support build
timestamps and releasing (for example adding a version number to pom.xml).
The SCM Commit Id can be stored in addition for cases where you might not
have clean releases to differentiate. For example with Jboss AS 7,
Is there a Git (plumbing) command, which can calculate a directories tree
hash (our print the tree object) without adding it to a (fake) index.
And on a similiar note, I havent found a way to force git status to run a
hash comparision for all files to verify the workdirectory state (ignoring
an