git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 10/10] lower core.maxTreeDepth default to 2048
Date: Thu, 31 Aug 2023 12:39:37 +0200	[thread overview]
Message-ID: <ZPBt6VYAWHJhv3N2@ugly> (raw)
In-Reply-To: <20230831062320.GJ3185325@coredump.intra.peff.net>

On Thu, Aug 31, 2023 at 02:23:20AM -0400, Jeff King wrote:
>But I thought that
>following the sequence of logic (from "4096 is probably OK" to "whoops,
>it's not") had some value to share.
>
of course, but you can just integrate that into the squashed commit 
message. having it all in one place makes it easier to follow.

regards

  reply	other threads:[~2023-08-31 10:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31  6:17 [PATCH 0/10] tree name and depth limits Jeff King
2023-08-31  6:17 ` [PATCH 01/10] tree-walk: reduce stack size for recursive functions Jeff King
2023-08-31  6:19 ` [PATCH 02/10] tree-walk: drop MAX_TRAVERSE_TREES macro Jeff King
2023-08-31  6:19 ` [PATCH 03/10] tree-walk: rename "error" variable Jeff King
2023-08-31  6:20 ` [PATCH 04/10] fsck: detect very large tree pathnames Jeff King
2023-08-31  6:21 ` [PATCH 05/10] add core.maxTreeDepth config Jeff King
2023-08-31  6:21 ` [PATCH 06/10] traverse_trees(): respect max_allowed_tree_depth Jeff King
2023-08-31  6:21 ` [PATCH 07/10] read_tree(): " Jeff King
2023-08-31  6:22 ` [PATCH 08/10] list-objects: " Jeff King
2023-08-31  6:22 ` [PATCH 09/10] tree-diff: " Jeff King
2023-08-31  6:23 ` [PATCH 10/10] lower core.maxTreeDepth default to 2048 Jeff King
2023-08-31 10:39   ` Oswald Buddenhagen [this message]
2023-08-31 17:42     ` Jeff King
2023-08-31 21:06       ` Junio C Hamano
2023-08-31 21:59         ` rsbecker
2023-08-31 22:31           ` Jeff King

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=ZPBt6VYAWHJhv3N2@ugly \
    --to=oswald.buddenhagen@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).