Skip to content
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

commands: only pass --jobs to 'git clone' if set #2369

Merged
merged 1 commit into from Jun 29, 2017

Conversation

technoweenie
Copy link
Contributor

Running git lfs clone always passes the --jobs option to git clone. This won't fly if you have git < 2.9:

error: unknown option `jobs'
usage: git clone [<options>] [--] <repo> [<dir>]

Fixes #2366 by setting the flag default to -1.

Copy link
Contributor

@ttaylorr ttaylorr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, and thanks for getting to this. None of the other flags added in #2252 should be affected by this since they are all strings and len(str) > 0 is the inclusion check for those.

@technoweenie
Copy link
Contributor Author

Ah, the reason our ci didn't catch this is because typically test against 3 git versions (on circle and travis):

  • Latest release
  • GIT_EARLIEST_SUPPORTED_VERSION which is 2.0.0.
  • Current master branch.

The GIT_EARLIEST_SUPPORTED_VERSION test should have caught this, but the clone test requires git 2.2.0+. Doh. I don't know if it's worth adding to the test matrix though.

@ttaylorr
Copy link
Contributor

ttaylorr commented Jul 6, 2017

The GIT_EARLIEST_SUPPORTED_VERSION test should have caught this, but the clone test requires git 2.2.0+. Doh. I don't know if it's worth adding to the test matrix though.

Ah, thanks for the explanation. This was very helpful. I think it's certainly worth poking around at to split out the tests that require Git 2.2.0+ and those that don't into separate test files. I don't have time to get to this immediately, but I've opened up #2391 to track this for the 2.3.0 release.

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

Successfully merging this pull request may close these issues.

None yet

2 participants