git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: Rohit Ner <rohitner1@gmail.com>,
	Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
	Derrick Stolee <derrickstolee@github.com>,
	git@vger.kernel.org
Subject: Re: git log causing hang while browsing upstream linux
Date: Sun, 16 Apr 2023 09:09:06 +0200	[thread overview]
Message-ID: <20230416070906.GA3271@szeder.dev> (raw)
In-Reply-To: <ZDSjBQhyDBGi9wBN@nand.local>

On Mon, Apr 10, 2023 at 08:00:05PM -0400, Taylor Blau wrote:
> On Mon, Apr 10, 2023 at 10:37:15PM +0530, Rohit Ner wrote:
> > I have not given the command more than 10 seconds, shouldn't the
> > intended behaviour be to render the visible subgraph first?
> 
> This is possible with Git's "commit-graph" feature, which you can read
> about starting here:
> 
> 		https://devblogs.microsoft.com/devops/supercharging-the-git-commit-graph/
> 
> TL;DR: if you run "git commit-graph write"

Please never recommend 'git commit-graph write' without '--reachable';
scanning all packed objects to find commits to include in the
commit-graph is just too inefficient for that.

> once before running "git log
> --oneline --graph", you'll get near-instantaneous results.

The commit-graph has been enabled by default in v2.24.0, released over
three years ago.  I wonder why Rohit's and/or Kristoffer's repos
didn't have it already?!


  parent reply	other threads:[~2023-04-16  7:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04 20:13 git log causing hang while browsing upstream linux Rohit Ner
2023-04-04 20:27 ` Kristoffer Haugsbakk
2023-04-04 20:50   ` Kristoffer Haugsbakk
2023-04-10 17:07     ` Rohit Ner
2023-04-11  0:00       ` Taylor Blau
2023-04-11  9:45         ` Kristoffer Haugsbakk
2023-04-16  7:09         ` SZEDER Gábor [this message]
2023-04-16 12:46           ` How to write to the commit graph on clone? Kristoffer Haugsbakk
2023-04-16 15:24             ` Ævar Arnfjörð Bjarmason

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=20230416070906.GA3271@szeder.dev \
    --to=szeder.dev@gmail.com \
    --cc=derrickstolee@github.com \
    --cc=git@vger.kernel.org \
    --cc=kristofferhaugsbakk@fastmail.com \
    --cc=me@ttaylorr.com \
    --cc=rohitner1@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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).