cyril@zarquon:~$ rm -rf ltupkgs/
cyril@zarquon:~$ git clone ssh://[email protected]/data/git/ltupkgs.git
Cloning into ltupkgs...
Enter passphrase for key '/home/cyril/.ssh/id_dsa':
warning: You appear to have cloned an empty repository.
cyril@zarquon:~$ cd ltupkgs/
cyril@zarquon:~/ltupkgs$ date > readme
cyril@zarquon:~/ltupkgs$ git add readme
cyril@zarquon:~/ltupkgs$ git commit -a
[master (root-commit) e7d54dc] date
 1 files changed, 1 insertions(+), 0 deletions(-)
 create mode 100644 readme
cyril@zarquon:~/ltupkgs$ git push origin master
Enter passphrase for key '/home/cyril/.ssh/id_dsa':
Counting objects: 3, done.
Writing objects: 100% (3/3), 250 bytes, done.
Total 3 (delta 0), reused 0 (delta 0)
remote: error: refusing to update checked out branch: refs/heads/master
remote: error: By default, updating the current branch in a non-bare repository
remote: error: is denied, because it will make the index and work tree inconsistent
remote: error: with what you pushed, and will require 'git reset --hard' to match
remote: error: the work tree to HEAD.
remote: error:
remote: error: You can set 'receive.denyCurrentBranch' configuration variable to
remote: error: 'ignore' or 'warn' in the remote repository to allow pushing into
remote: error: its current branch; however, this is not recommended unless you
remote: error: arranged to update its work tree to match what you pushed in some
remote: error: other way.
remote: error:
remote: error: To squelch this message and still keep the default behaviour, set
remote: error: 'receive.denyCurrentBranch' configuration variable to 'refuse'.
To ssh://[email protected]/data/git/ltupkgs.git
 ! [remote rejected] master -> master (branch is currently checked out)
error: failed to push some refs to 'ssh://[email protected]/data/git/ltupkgs.git'