All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arun Sharma <arun@sharma-home.net>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
	Arun Sharma <arun@sharma-home.net>,
	git@vger.kernel.org
Subject: Re: bug report: mutual recursion in the git-subtree shell script
Date: Sun, 14 Mar 2021 10:31:11 -0700	[thread overview]
Message-ID: <CAN7rbOuOaHY553KX1Qcr_XWGG6DFo1yUjdYVu5mn=HYPmOj6vQ@mail.gmail.com> (raw)
In-Reply-To: <YEzwOqgFcva4fmoV@camp.crustytoothpaste.net>

On Sat, Mar 13, 2021 at 9:03 AM brian m. carlson
<sandals@crustytoothpaste.net> wrote:
>
> I don't use git-subtree, but there's some additional information which
> would probably be helpful here to someone who does.  What OS are you
> using, what version of Git, and what shell is the shell you have as
> /bin/sh (or, if you've compiled using a custom shell, the shell you're
> using for that)?

Thanks for the hint. 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)

It could take several minutes because of the size of the repo.

And then try to pull the latest version and push the merged result
into the smaller subproject.

 -Arun

  reply	other threads:[~2021-03-14 17:32 UTC|newest]

Thread overview: 4+ 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 [this message]
2021-03-15  5:19     ` Johannes Schindelin

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='CAN7rbOuOaHY553KX1Qcr_XWGG6DFo1yUjdYVu5mn=HYPmOj6vQ@mail.gmail.com' \
    --to=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 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.