Tag Info

New answers tagged

3

There's no difference. HEAD is entirely optional. HEAD normally points to the last commit of the current branch. If you don't use it, it's implied. It makes sense only if you want to reset file based on some different branch or commit etc. In other words, it makes sense to use something else than HEAD. git checkout with -- is safer. It's clear that ...


1

Use another processes as a middle-man. Your web service (or whatever) writes new requests to a spool somewhere. The middle-man watches the spool, removes and sanity checks new entries, and append what's valid to git's authorized_keys file. The same middle-man can give feedback that the web service can read. But a compromised http user cannot manipulate ...


0

Since you are fine with letting untrusted users add their public keys to the authorized_keys file of the git user, then you might as well let them know the password for git.


1

git config --global color.ui auto git config --global color.branch auto git config --global color.status auto


3

Here are the commands you need to run, if you just want to get it done: sudo add-apt-repository ppa:git-core/ppa -y sudo apt-get update sudo apt-get install git git --version As of Dec 2014, I get git 2.2.0 that way, while the version in the Ubuntu Trusty repositories is 1.9.1.



Top 50 recent answers are included