Re: fatal: bad numeric config value '60 days' for 'gc.rerereresolved': invalid unit

Yeah, after I checked the code I saw that this is interpreted as integer and fixed my configuration 2017-07-21 16:33 GMT+02:00 Junio C Hamano <gits...@pobox.com>: > Uwe Hausbrand <uwe.hausbr...@gmx.de> writes: > >> seems like there is a bug with "git rerere gc"

fatal: bad numeric config value '60 days' for 'gc.rerereresolved': invalid unit

Hi all, seems like there is a bug with "git rerere gc" not understanding grace periods like "60 days" defined in the config. What I did: git config gc.rerereresolved "60 days" git gc results in: Counting objects: 158790, done. Delta compression using up to 8 threads. Compressing objects: 100%

pre-rebase, post-rewrite, ...

Hi all, I am using the pre-rebase hook to generate a tag. I am using this tag to check if my rebase lost any commits or content when i'm cleaning up my local commit history. What i now want to do is using a post-rebase hook to make a diff check and remove my generated tag in case there is no