Re: Regression in git-subtree.sh, introduced in 2.20.1, after 315a84f9aa0e2e629b0680068646b0032518ebed

> [...] > >> > > Hmm.. I'm not that familiar with git-subtree.sh, so here's one last > blind shot. > > There's a format change between git-show and git-rev-parse. The former > separates commits by spaces while the latter by newlines. Will this > help? > > diff --git a/contrib/subtree/git-su

Re: Regression in git-subtree.sh, introduced in 2.20.1, after 315a84f9aa0e2e629b0680068646b0032518ebed

> Am 31.12.2018 um 12:36 schrieb Duy Nguyen : > > On Mon, Dec 31, 2018 at 6:24 PM Marc Balmer wrote: >> In a (private) Email to me, he indicated that had no time for a fix. Maybe >> he can speak up here? > > Well, I guess Junio will revert when he'

Re: Regression in git-subtree.sh, introduced in 2.20.1, after 315a84f9aa0e2e629b0680068646b0032518ebed

> Am 31.12.2018 um 12:20 schrieb Duy Nguyen : > > On Mon, Dec 31, 2018 at 6:13 PM Marc Balmer wrote: >> >> >> >>> Am 31.12.2018 um 11:51 schrieb Duy Nguyen : >>> >>> On Mon, Dec 31, 2018 at 5:44 PM Marc Balmer wrote: >>

Re: Regression in git-subtree.sh, introduced in 2.20.1, after 315a84f9aa0e2e629b0680068646b0032518ebed

> Am 31.12.2018 um 11:51 schrieb Duy Nguyen : > > On Mon, Dec 31, 2018 at 5:44 PM Marc Balmer wrote: >> >> Hi >> >> One of the last three commits in git-subtree.sh introduced a regression >> leading to a segfault. >> >> Here is the

Regression in git-subtree.sh, introduced in 2.20.1, after 315a84f9aa0e2e629b0680068646b0032518ebed

Hi One of the last three commits in git-subtree.sh introduced a regression leading to a segfault. Here is the error message when I try to split out my i18n files: $ git subtree split --prefix=i18n cache for e39a2a0c6431773a5d831eb3cb7f1cd40d0da623 already exists! (Lots of output omitted) 436