all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Tip: git commit-graph
Date: Wed, 11 Oct 2023 20:30:54 +0200	[thread overview]
Message-ID: <m2pm1lm2ox.fsf@Pro.fritz.box> (raw)
In-Reply-To: <CAP_d_8VsH=gLKL+UVCJ8_Swch7sxz7y3sf7LgCWNCz92k9LRVQ@mail.gmail.com> (Yuri Khan's message of "Thu, 12 Oct 2023 00:53:55 +0700")

Yuri Khan <yuri.v.khan@gmail.com> writes:

>> In the recently released Git version 2.24.0, the commit-graph is enabled by default!
>
> but what it actually seems to mean is that 2.24 changes the defaults
> for two configuration variables to ‘true’:
>
> * ‘core.commitGraph’ which instructs Git to *use* the file if present; and
> * ‘gc.writeCommitGraph’ which instructs it to *create or update* the
> file on every invocation of ‘git gc’.

In addition to that I've added

  git config --global fetch.writeCommitGraph true

I think that's also from the article, not sure anymore.  And the write
I've done with

  git commit-graph write --reachable --changed-paths

because somewhere else it was suggested that that helps with the log of
single files.

> So this answers my question: Users who have not run ‘git gc’ since
> 2019, or ‘git commit-graph write’ ever, will not already have a
> serialized commit graph.

:-)



      reply	other threads:[~2023-10-11 18:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11 10:51 Tip: git commit-graph Gerd Möllmann
2023-10-11 16:17 ` Fu Yuan
2023-10-11 17:12 ` Yuri Khan
2023-10-11 17:25   ` Gerd Möllmann
2023-10-11 17:53     ` Yuri Khan
2023-10-11 18:30       ` Gerd Möllmann [this message]

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=m2pm1lm2ox.fsf@Pro.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=yuri.v.khan@gmail.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.