Git is confused, because 12382 looks like a commit hash. Use the fully qualified name to checkout the branch: git checkout refs/heads/12382 — or, if it’s a remote branch: git checkout refs/remotes/origin/12382 —
No. A git-svn clone converts the entire repository into git. SVN checkouts do not have the entire repository and so cannot be cloned from. This is the primary advantage of switching from SVN or CVS to a distributed system (like git).
mygithub/master is a remote branch. To create a local branch based off of that remote branch, you have to use git checkout -b mymaster mygithub/master. Git tries to make this easy for you: if you write git checkout branchname, and branchname only exists in a remote, but not locally, Git will automatically set up a … Read more
Try: git config –system core.longpaths true This will allow it to checkout the files even with longer filepaths. The issue with this would be when you try to delete it, as Windows will not allow to delete a path longer than it’s allowed threshold. The workaround to that is to rename the folders in the … Read more
Assuming the hash of the commit you want is c5f567: git checkout c5f567 — file1/to/restore file2/to/restore The git checkout man page gives more information. If you want to revert to the commit before c5f567, append ~1 (where 1 is the number of commits you want to go back, it can be anything): git checkout c5f567~1 … Read more
Git is warning you that forms/answers.php has changes in your working copy or index that have not been committed. You can use git-stash to save your changes then git-stash apply to restore them. The common use case of git-stash is that you are working on changes but then must temporarily checkout a different branch to … Read more
I had a similar situation. Though it was due to me having the solution open in visual studio. Closing visual studio and doing a git reset put me into a good spot. I.e. check to see if any processes are locking the folder/files.
I think you want this: git symbolic-ref -q –short HEAD || git describe –tags –exact-match That will output the value of HEAD, if it’s not detached, or emit the tag name, if it’s an exact match. It’ll show you an error otherwise.
This error message comes from this patch (in compat/mingw.c), and this one (also in compat/mingw.c). It usually means your directory is “busy”, or isn’t empty (but contains only private files, ie non-versioned files). So make sure that, when checking out a branch, you don’t have a running process making your specific directory “busy”. Ted M … Read more
OP wanted to retrieve all versions, but the answers would not deliver. Especially if the file has hundreds of revisions (all suggestions are too manual). The only half-working solution was proposed by @Tobias in the comments, but suggested bash loop would build files in random order as well as it generates hundreds of empty files … Read more