git archive can work with a server with git protocol support (i.e. git server, smart-http and ssh server). In your case, either your git is too old, or the server is dumb http server (normal http server, without “smart” git support). You need to clone the repository and archive from there.
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
You can use –git-dir to specify the .git directory to use as the repository, and –work-tree to specify the working tree to to the checkout in. See the git man page for details. git –git-dir=file-system-folder/.git –work-tree=file-system-folder checkout existing-branch
The Short Answer As long as you’re doing a fast-forward merge, then you can simply use git fetch <remote> <sourceBranch>:<destinationBranch> Examples: # Merge local branch foo into local branch master, # without having to checkout master first. # Here `.` means to use the local repository as the “remote”: git fetch . foo:master # Merge … Read more
It’s mostly a quirk of how git checkout works internally. The Git folks have a tendency to let implementation dictate interface. The end result is that after git checkout with –ours or –theirs, if you want to resolve the conflict, you must also git add the same paths: git checkout –ours — path/to/file git add … Read more
I generally find it unnecessary to use git fetch. git pull is sufficient. git pull will synchronize your repository with the remote. The new_feature_branch will then be available. git checkout new_feature_branch will notice the branch in origin and create a new local tracking branch for you and switch to that branch. git pull git checkout … Read more
This answer is mostly quoted from my answer to a previous question: git reset in plain english. The two are very different. They result in the same state for your index and work tree, but the resulting history and current branch aren’t the same. Suppose your history looks like this, with the master branch currently … Read more
Try this instead of git checkout: git symbolic-ref HEAD refs/heads/develop Then you should be able to delete master.
Like vcsjones says, the solution here is git checkout: git checkout <refspec> — path/to/directory # or path/to/file where <refspec> can, for instance, be HEAD, that is, the current working commit. Note that this usage of the checkout command will affect the working tree but not the index. git revert is used to “revert a commit”, … Read more
Summary: You can use Git’s reflog to show recent movements in order of checkout: git reflog Script: Here’s a script you can download and use via git recent from inside any Git repository: https://gist.github.com/jordan-brough/48e2803c0ffa6dc2e0bd Usage: $ (master) git recent -n 5 1) master 4) deleted-branch 2) stable 5) improve-everything 3) fun Choose a branch: 2 … Read more