New answers tagged

1

The cat command results must be expanded using command substitution. The syntax for bash is: curl -u "user:pass" --data '{"title":"test-key","key":"'"$(cat ~/.ssh/id_rsa.pub)"'"}' https://api.github.com/user/keys You can also use a classic backtick notation: curl -u "user:pass" --data '{"title":"test-key","key":"'`cat ~/.ssh/id_rsa.pub`'"}' https://api....


1

checkout the remote stable branch git fetch <remote> <branch> Your local repo will now have a read only copy of the remote tracking branch, now check out to the read only tracking branch git checkout origin/<branch_name> Your VCS (whatever you are using) will start show messages like: HEAD is in a detached state Previous HEAD ...


0

This is most likely a Dns Problem try pinging google.com ping google.com it won't work if it is actually a DNS problem. In That case vi /etc/resolv.conf and set ur dns servers with changing/adding those lines. nameserver 8.8.8.8 nameserver 8.8.4.4


0

Is there a firewall/proxy in place restriciting access? Can you clone via SSH (note: you'll need a GitHub account and need to add your public SSH key to your profile to be able to SSH in). git clone ssh://git@github.com/Rishav09/Mywebsite.git


1

You seem to have a directory whose name consists entirely of non-printable and whitespace characters. You can use a wildcard to match it: mv -i [^A-Za-z0-9_]* renamed This prompts you to move all files whose name don't begin with a letter, a digit or an underscore. There's probably only that one file. Alternatively, if your shell is set up to iterate ...


1

You have managed to create a directory with a space (or several) as its name. Rename it: mv " "* I_see_you In the case that it's not a simple space, you could try replacing any non graphical characters with X: $ # (having moved everything else away to a safe place...) $ for d in *; do test -d "$d" && echo mv "$d" "$( tr -c '[:graph:]' 'X' <&...


0

git config --global color.ui always git config --global color.branch always git config --global color.diff always git config --global color.interactive always git config --global color.status always git config --global color.grep always git config --global color.pager true git config --global color.decorate always git config --global color.showbranch always


1

Solved. I am speechless. I had made a quick check for a ~/.git-whatever file using bash autocompletion (tab), it did not work so I blindly assumed the issue was somewhere else. Patrick's comment shed the light: I carefully checked using ls -a ~/, the ~/.gitconfig he wrote about really is here, and it holds the information regarding the remote: $ cat ~/....


2

I have successfully used ikiwiki with 0+ repositories. 0..2 are single-user, so I have not run into conflicts (yet). 0..1 were just an experiment with ikiwiki. Here is what I tried: 0 repositories - compiling manually, 1 repository (working directory == srcdir) without upstream - compiling manually, 2 repositories (working directory == srcdir + upstream) ...


0

I've been fetching my local Git repos in the background for two years now, without any sign of trouble.



Top 50 recent answers are included