-
Notifications
You must be signed in to change notification settings - Fork 13
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
usage of fetch #12
Comments
Requiring an existing directory was most likely unintentional. Again, I encourage you to make a pull request to fix the problem. |
Ok, I will, but allow me to understand how usage was meant to work. git-lfs-fetch.py/git_lfs/__init__.py Lines 163 to 169 in 23026ff
Why the |
Creating a temporary file or directory, then renaming it, is a way of making changes atomically. I don't remember if the code was written this way merely as a precaution or if I actually needed this “safety” at the time. |
Understood. It would help if you could divulge one concrete example of a call (API or CLI) that used to succeed. I'm sure I can take it from there and reconstruct the intended implementation. |
The call was |
Oh, then my impression that this was also meant for remote repos (first cloning https or git URLs) was wrong to begin with? |
The code was never meant to be invoked with URLs of remote repositories. |
I am having difficulty understanding how to use
fetch
. If I do not pass acheckout_dir
(which I would expect to be generated from the last path component ofgit_repo
as ingit clone URL
), then it saysCan't checkout into a bare repo
. If I do pass somecheckout_dir
, then I run into this:So this obviously expects an existing directory. Why?
The text was updated successfully, but these errors were encountered: