public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Colin Stagner <ask+git@howdoi.land>
To: Arun Sharma <arun@sharma-home.net>
Cc: git@vger.kernel.org, "brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: bug report: mutual recursion in the git-subtree shell script
Date: Sat, 14 Mar 2026 16:36:27 -0500	[thread overview]
Message-ID: <454235b2-139f-40bd-a4ac-fb7664962471@howdoi.land> (raw)
In-Reply-To: <CAN7rbOuOaHY553KX1Qcr_XWGG6DFo1yUjdYVu5mn=HYPmOj6vQ@mail.gmail.com>

Arun,

I found your git-subtree bug report from several years ago.

On 3/13/21 10:06, Arun Sharma wrote:

> So I'm trying to split out a directory from postgres source code
> (which has 52k commits).
> 
> $ git subtree push --prefix=src/interfaces/libpq libpq master
> /usr/lib/git-core/git-subtree: 647: Maximum function recursion depth
> (1000) reached

On 3/14/21 12:31, Arun Sharma wrote:

> I was using ubuntu 20.04.
> 
> $ git --version
> git version 2.25.1
> 
> $ bash --version
> GNU bash, version 5.0.16(1)-release (x86_64-pc-linux-gnu)
> 
> To repro, you can try to split a week old version of:
> 
> https://github.com/postgres/postgres (subtree: src/interfaces/libpq)

Is this issue still relevant to you?

I have prepared a patch series that I hope will correct this problem. If 
you have the time, can you please test and review:

<https://lore.kernel.org/git/20260305-cs-subtree-split-recursion-v2-0-7266be870ba9@howdoi.land/>

Code reviews are eagerly solicited.

Colin


      parent reply	other threads:[~2026-03-14 21:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-13 16:06 bug report: mutual recursion in the git-subtree shell script Arun Sharma
2021-03-13 17:02 ` brian m. carlson
2021-03-14 17:31   ` Arun Sharma
2021-03-15  5:19     ` Johannes Schindelin
2026-03-14 21:36     ` Colin Stagner [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=454235b2-139f-40bd-a4ac-fb7664962471@howdoi.land \
    --to=ask+git@howdoi.land \
    --cc=arun@sharma-home.net \
    --cc=git@vger.kernel.org \
    --cc=sandals@crustytoothpaste.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