Trying to install Hugo via Homebrew – “Could Not Resolve HEAD to a Revision”
Use git -C $(brew –repository homebrew/core) checkout master or git -C $(brew –repository homebrew/core) reset –hard HEAD
Use git -C $(brew –repository homebrew/core) checkout master or git -C $(brew –repository homebrew/core) reset –hard HEAD
You can bind mount the submodule’s other directory sudo mount –bind /path/to/main/repo relative/path/to/submodule I can’t find much info about this method, but saw it listed in this, similar question.
I just set something like this up at work using pip, Fabric and git. The flow is basically like this, and borrows heavily from this script: In our source tree, we maintain a requirements.txt file. We’ll maintain this manually. When we do a new release, the Fabric script creates an archive based on whatever treeish …
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.
The following pre-receive hook will block those: #/bin/bash # Copyright (c) 2016 G. Sylvie Davies. http://bit-booster.com/ # Copyright (c) 2016 torek. http://stackoverflow.com/users/1256452/torek # License: MIT license. https://opensource.org/licenses/MIT while read oldrev newrev refname do if [ “$refname” = “refs/heads/master” ]; then MATCH=`git log –first-parent –pretty=’%H %P’ $oldrev..$newrev | grep $oldrev | awk ‘{ print \$2 }’` …
There is no easy way to accomplish this without further work. After playing with it for a little while I have something that might help you. git bisect start master f9d5924 for rev in $(git rev-list f9d5924..master –merges –first-parent); do git rev-list $rev^2 –not $rev^ done | xargs git bisect skip This starts git bisect …
Here’s an adaptation from a related question. git diff -w –no-color | git apply –cached –ignore-whitespace It has the benefit that you don’t need to use stash, temporary files, or perform a reset –hard on your working folders. Addendum The solution above only stages changes except whitespace-only edits. This did not address patch, though using …
Given the following test-setup: git init resolving-rename-conflicts cd resolving-rename-conflicts echo “this file we will rename” > will-be-renamed.txt git add -A git commit -m “initial commit” git checkout -b branch1 git rename will-be-renamed.txt new-name-1.txt git commit -a -m “renamed a file on branch1” git checkout -b branch2 master git rename will-be-renamed.txt new-name-2.txt git commit -a -m …
You can run git rebase –abort to completely undo the rebase. Git will return you to your branch’s state as it was before git rebase was called. You can run git rebase –skip to completely skip the commit. That means that none of the changes introduced by the problematic commit will be included. It is …