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

cloning a new fork doesn't transfer all directories #8086

Open
ndhananj opened this issue Sep 3, 2017 · 1 comment
Open

cloning a new fork doesn't transfer all directories #8086

ndhananj opened this issue Sep 3, 2017 · 1 comment

Comments

@ndhananj
Copy link

ndhananj commented Sep 3, 2017

I tried modifying my config for path names. That didn't help.

@ndhananj
Copy link
Author

ndhananj commented Sep 3, 2017

Okay. I needed to run git bash as administrator. This allowed the config line to actually work.

It wasn't the clone that was failing but the checkout after the clone, because of the long path names.

When I run git bash as an administrator, it allowed the git config --system command to actually run,

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

No branches or pull requests

1 participant