Skip to content

gic {init,clone} --separate-git-dir is supported only since 1.7.5 #324

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

Merged
merged 1 commit into from
Jul 22, 2015

Conversation

roidelapluie
Copy link
Contributor

Without this commit the update() function of a submodule does not work
in CentOS 6.

Without this commit the update() function of a submodule does not work
in CentOS 6.
@Byron
Copy link
Member

Byron commented Jul 22, 2015

Thank you !
I did my best to figure out when the feature was introduced, and found it difficult to find good documentation about it in the changelog.
Let's hope that patch-level 5 will work everywhere.

@Byron Byron added this to the v1.0.2 - Fixes milestone Jul 22, 2015
Byron added a commit that referenced this pull request Jul 22, 2015
gic {init,clone} --separate-git-dir is supported only since 1.7.5
@Byron Byron merged commit 11b3a1d into gitpython-developers:master Jul 22, 2015
@roidelapluie
Copy link
Contributor Author

I did a git blame on https://github.com/git/git/blob/01977f46cb48e2894e335667eaabce274174ac5e/builtin/clone.c

Which shows git/git@b57fb80

Which is tagged 1.7.5.

In CentOS 6:
$ git --version
git version 1.7.1

@Byron
Copy link
Member

Byron commented Jul 22, 2015

Thanks again for digging deeper than I did ! With that information I believe there is certainty that GitPython can now make the correct decisions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants