git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
MÅMartin Ågren <martin.agren@gmail.com>
Date
Jul 21, 2017, 14:30 UTC
Message-ID
<CAN0heSrQv=TjjE_=9PC14Ob2dn9g4Qq0Vm+yPoh6hmGzd1W_Uw@mail.gmail.com>
In-Reply-To
<CAHNyMp8xeye8EvtOdrX34QVCDsBCu3aLQVdyGRTVqyHXjZ4FFQ@mail.gmail.com>
On 21 July 2017 at 14:59, Uwe Hausbrand <uwe.hausbrand@gmx.de> 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 not entirely clear, but "man git-gc" does seem to suggest -- at least to me -- that one can say "60 days". Especially after reading about gc.reflogExpire a few paragraphs earlier, where "90 days" and "3 months" are given as examples. Luckily, "man git-config" is a bit clearer. It says that "records ... are kept for this many days". The latter matches the implementation and the tests, which are all written to work with just an integer.

So "git config gc.rerereresolved 60" should work. Hope that helps.
Martin
Previous: Uwe HausbrandNext: Junio C Hamano
Message 2 of 16 in “fatal: bad numeric config value '60 days' for 'gc.rerereresolved': invalid unit”
  1. Uwe HausbrandJul 21, 2017
  2. Martin ÅgrenJul 21, 2017
  3. Junio C HamanoJul 21, 2017
  4. Uwe HausbrandJul 21, 2017
  5. 0/2 accept non-integer for "this many days" expiry specificationJunio C Hamano, Aug 19, 2017
  6. 2/2 rerere: allow approxidate in gc.rerereResolved/gc.rerereUnresolvedJunio C Hamano, Aug 19, 2017
  7. Ramsay JonesAug 20, 2017
  8. Junio C HamanoAug 21, 2017
  9. 1/2 rerere: represent time duration in timestamp_t internallyJunio C Hamano, Aug 19, 2017
  10. 0/6 accept non-integer for "this many days" expiry specificationJunio C Hamano, Aug 22, 2017
  11. 1/6 t4200: give us a clean slate after "rerere gc" testsJunio C Hamano, Aug 22, 2017
  12. 3/6 t4200: gather "rerere gc" togetherJunio C Hamano, Aug 22, 2017
  13. 2/6 t4200: make "rerere gc" test more robustJunio C Hamano, Aug 22, 2017
  14. 4/6 t4200: parameterize "rerere gc" custom expiry testJunio C Hamano, Aug 22, 2017
  15. 5/6 rerere: represent time duration in timestamp_t internallyJunio C Hamano, Aug 22, 2017
  16. 6/6 rerere: allow approxidate in gc.rerereResolved/gc.rerereUnresolvedJunio C Hamano, Aug 22, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.