ELI <eliptus@xxxxxxxxx> writes: > I then reviewed the commit history of contrib/subtree/git-subtree.sh > and determined that the last successful subtree push was performed > prior to the integration of this change: > https://git.kernel.org/cgit/git/git.git/commit/contrib/subtree/git-subtree.sh?id=933cfeb90b5d03b4096db6d60494a6eedea25d03 > > As a next step, I reversed that patch on my local install of git > subtree, and the result was a successful subtree push. So you're saying that this patch caused a regression? > Unfortunately, I have not yet reproduced this with a test main project > and subprojects, and I cannot make the project I observed it in > public. I very much want to see a testcase for this. I'm planning to fundamentally rewrite the split code this year and want to make sure it covers everything it does now and fixes a few bugs that have been exposed lately. It's tough to revert that patch since it fixed a problem for someone and we don't have a testcase demonstrating the problem you encountered. Not saying your problem isn't important but we need to understand it and have a way to flag it before fixing or hiding it with a revert of the above patch. -David -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html