Git development
 help / color / mirror / Atom feed
From: Teemu Likonen <tlikonen@iki.fi>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: git@vger.kernel.org, mercurial@selenic.com
Subject: Re: how to squash commits
Date: Sun, 12 Apr 2009 18:39:10 +0300	[thread overview]
Message-ID: <871vrxlw4h.fsf@iki.fi> (raw)
In-Reply-To: <vpqocv1vr1y.fsf@bauges.imag.fr> (Matthieu Moy's message of "Sun\, 12 Apr 2009 17\:18\:33 +0200")

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.

http://www.kernel.org/pub/software/scm/git/docs/git-gc.html

       reply	other threads:[~2009-04-12 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <85b5c3130904111627l7cdd15a1n78271c8e113c4b7a@mail.gmail.com>
     [not found] ` <cd4419280904120508v37314166pb35db8b50ec54839@mail.gmail.com>
     [not found]   ` <87d4bhlxlf.fsf@iki.fi>
     [not found]     ` <vpqocv1vr1y.fsf@bauges.imag.fr>
2009-04-12 15:39       ` Teemu Likonen [this message]
2009-04-12 15:54         ` how to squash commits Matthieu Moy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871vrxlw4h.fsf@iki.fi \
    --to=tlikonen@iki.fi \
    --cc=Matthieu.Moy@imag.fr \
    --cc=git@vger.kernel.org \
    --cc=mercurial@selenic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox