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

Re: how to squash commits

From
Matthieu Moy <matthieu.moy@imag.fr>
Date
Apr 12, 2009, 15:54 UTC
Message-ID
<vpq1vrxvpel.fsf@bauges.imag.fr>
In-Reply-To
<871vrxlw4h.fsf@iki.fi>
Teemu Likonen <tlikonen@iki.fi> writes:
Show 24 quoted lines
> Let's add the Git mailing list to the Cc list if someone there wants to
> comment. The whole thread is here:
>
> http://thread.gmane.org/gmane.comp.version-control.mercurial.general/13283/focus=13295
>
>
> On 2009-04-12 17:18 (+0200), Matthieu Moy wrote:
>
>> Teemu Likonen <tlikonen@iki.fi> writes:
>>
>>> With the default settings user has 30 days to
>>> recover the branch's previous state,
>>
>> Actually, s/30 days/90 days/ according to "man git-gc".
>
> I understand it that objects which are not reachable form the tip of
> current branches are subject for garbage-collecting in 30 days. For
> example, let's say we are in "master" branch and do "git reset --hard
> master~1". It makes the previous HEAD commit unreachable from "master"
> branch and it can be GCd in 30 days (?).
>
> My understanding can be wrong, of course. The manual explainst options
> like gc.reflogExpire and gc.reflogExpireUnreachable separately but does
> not draw the big picture how things work.

Oops, I think you're right. I didn't read about gc.reflogExpireUnreachable carrefully enough.

-- 
Matthieu
Previous: Teemu Likonen
Message 2 of 2 in “Re: how to squash commits”
  1. Teemu LikonenApr 12, 2009
  2. Matthieu MoyApr 12, 2009

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.