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

2017-07-21 Thread Uwe Hausbrand
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 : > Uwe Hausbrand writes: > >> seems like there is a bug with "git rerere gc" not understanding grace >> periods like "60 days" defined in the config. >> >

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

2017-07-21 Thread Junio C Hamano
Uwe Hausbrand writes: > 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" Let's see how the variable is explained in the documentation. gc.rerereResolved::

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

2017-07-21 Thread Martin Ă…gren
On 21 July 2017 at 14:59, Uwe Hausbrand wrote: > git config gc.rerereresolved "60 days" > git gc > > results in: [...] > fatal: bad numeric config value '60 days' for 'gc.rerereresolved': invalid > unit > error: failed to run rerere It's n

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

2017-07-21 Thread Uwe Hausbrand
eads. Compressing objects: 100% (26849/26849), done. Writing objects: 100% (158790/158790), done. Total 158790 (delta 116114), reused 158790 (delta 116114) fatal: bad numeric config value '60 days' for 'gc.rerereresolved': invalid unit error: failed to run rerere git --version = git version 2.13.0 Best regards, Uwe