forked from git/git
- Notifications
You must be signed in to change notification settings - Fork 2.8k
Closed
Labels
Description
Setup
- Which version of Git for Windows are you using? Is it 32-bit or 64-bit?
$ git --version --build-options git version 2.19.0.windows.1 cpu: x86_64 built from commit: d96bb8bc6c636a8869140e860e72e7bdf64bd790 sizeof-long: 4 sizeof-size_t: 8 - Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?
$ cmd.exe /c ver Microsoft Windows [Version 6.1.7601] - What options did you set as part of the installation? Or did you choose the
defaults?
> type "C:\Program Files\Git\etc\install-options.txt" Editor Option: Nano Path Option: Cmd SSH Option: OpenSSH CURL Option: OpenSSL CRLF Option: CRLFAlways Bash Terminal Option: MinTTY Performance Tweaks FSCache: Enabled Use Credential Manager: Enabled Enable Symlinks: Enabled Enable Builtin Rebase: Disabled Enable Builtin Stash: Disabled - Any other interesting things about your environment that might be related
to the issue you're seeing?
Nope
Details
- Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other
CMD
- What commands did you run to trigger this issue? If you can provide a
Minimal, Complete, and Verifiable example
this will help us understand the issue.
git clone --jobs=10 --branch=develop --depth=1 --no-tags --recurse-submodules --shallow-submodules https://github.com/boostorg/boost.git - What did you expect to occur after running these commands?
I expect to see cloning and checkout things go in parallel.
- What actually happened instead?
It goes sequentially, so there is no actual difference between --jobs=10 and --jobs=1.
In Process Explorer I see how one by one git.exe processes are spawned and never seen multiple simultaneously.
The timings are following: on Windows - 5 minutes for cloning Boost, on Linux - 30 seconds.
- If the problem was occurring with a specific repository, can you provide the
URL to that repository to help us with testing?