-
Notifications
You must be signed in to change notification settings - Fork 278
error: unknown option `--initial-branch=master' with git version 2.25.1 #1969
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'd say reverting that change and living with the warnings is okay for M2, if that's the easiest thing, and then one of the other options is better for the beta. |
/cc @ceedubs |
Sorry for the trouble. I don't really have capacity to help with a change at the moment, but I would have no heartburn about reverting the change for now. At some point relying on a global git version might be a problem that we want to address in the various distributions. Or maybe at some point with the new code base format git won't be needed at all? |
@ceedubs No worries (it seemed like a good idea at the time) and thanks for the input. Yes, at some point git won't be needed at all, because we'll want our own transfer protocol (inspired by git-pack) instead of shipping around full databases anyway; or some other efficient thing. |
For M2 we're just going to revert this and people will see this annoying warning until it's fixed in a more robust way. |
Uh oh!
There was an error while loading. Please reload this page.
In #1834 we added this flag to suppress a warning that appeared in the newest versions of git, but it's not backwards-compatible with even fairly recent versions of git, which will instead exit with an error.
This came up on a digital ocean box running Ubuntu 20.04.1 LTS.
Possible solutions:
git --version
, parse the result, and issue different commands depending on the outcomeREADME.md
or other supplemental files a publisher has stored in their repo.The text was updated successfully, but these errors were encountered: