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

Re: repository corruption when pushing commits to a repository running 'git gc --prune='

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 14, 2015, 21:39 UTC
Message-ID
<xmqqfv1d6sg0.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<vpqtwpt6tsv.fsf@grenoble-inp.fr>
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
Show 12 quoted lines
> Junio C Hamano <gitster@pobox.com> writes:
>
>> Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
>>
>>> Looks good to me. I think the same should be added to git-prune.txt
>>> under --expire.
>>
>> I thought about it, but decided against it, as the command is not
>> even recommended to end users.
>
> Even non-"end users" can shoot themselves in the foot. Someone writting
> a script using "git prune" may actually shoot in other people's foot ...
Sure, patches welcome.
To be honest, I felt that
    --expire <time>::
            Only expire loose objects older than <time>.
is sufficiently clear for these people.
Previous: Matthieu MoyNext: Matthieu Moy
Message 7 of 10 in “repository corruption when pushing commits to a repository running 'git gc --prune='”
  1. Jan SmetsOct 14, 2015
  2. Matthieu MoyOct 14, 2015
  3. Junio C HamanoOct 14, 2015
  4. Matthieu MoyOct 14, 2015
  5. Junio C HamanoOct 14, 2015
  6. Matthieu MoyOct 14, 2015
  7. Junio C HamanoOct 14, 2015
  8. Matthieu MoyOct 14, 2015
  9. Junio C HamanoOct 14, 2015
  10. Matthieu MoyOct 14, 2015

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.