gitolite

I am trying to use Gitolite + Gitweb but I am running into some problems.. My conf/gitolite.conf is the following @dataset_repos = dat1 dat2 @closedsrc_repos = cod1 cod2 @opensrc_repos = testing @admins = user1 user2 @bios = user1 user2 user3 @coders = user1 user3 repo gitolite-admin RW+ = @admins repo @opensrc_repos RW+ = @all repo @dataset_repos RW+ = @admins @bios repo @closedsrc_repos RW+ = @admins @coders When I first inserted repository code1 and code2, git told me: remote: Initialized empty Git repository in /home/git/repositories/code1.git/ remote: Initialized empty Git repository in

git clone git@ubuntu-12.04-LTS:gitolite-admin.git 如果克隆失败，需要 git clone git@ubuntu-12.04-LTS:repositories/gitolite-admin.git 即可， 如果还是失败, 需要 git clone git@ubuntu-12.04-LTS:/home/git/repositories/gitolite-admin.git 来源： oschina 链接： https://my.oschina.net/u/1387344/blog/656028

I'm trying to set up a gitolite instance, and running into a problem where I follow the usual procedure to add a user (i.e. add public key file to keydir/xxx.pub; commit and push upstream) but then I'm finding that I can't clone repositories using the key I added. I've verified that the commit I've made (adding the public key) to gitolite-admin is successfully pushed upstream (i.e. to the bare gitolite-admin repo within the gitolite installation). I've noticed that no corresponding change was made to the authorized_keys file of the "gitolite" user, which seems wrong to me - I would expect to

After some digging and help here from other people , I found out that I have a problem with the umask setting in git. What I want to achieve is that any git repo that is being checked out on my server, that the umask setting defaults to 0002. I don't want to have to configure this in every post-receive hook... I want this to be the default umask . How do I achieve that? My repositories are uploaded by logging in to ssh with the git user on the server. When I check the umask setting, this is already set to the right setting: root@server:~# su git git@server:~$ umask 0002 However, if I put umask

I am going nuts with a problem cloning the gitolite-admin repository. I have followed this http://sitaramc.github.com/gitolite/install.html#migr and it went perfectly. I ran ssh-keygen -t rsa and scp ~/.ssh/id_rsa.pub morten@ubuntu-server:/tmp/morten.pub authorized_keys on the server looks like this: # gitolite start command="/home/morten/gitolite/src/gitolite-shell morten",no-port-forwarding,no-X11-forwarding,no-agent-forward$ # gitolite end Which AFAIK is okay. When I run git clone morten@ubuntu-server:gitolite-admin on my client, I get fatal: 'gitolite-admin' does not appear to be a git

I have tried the following command and it fails. git push origin :next remote: error: denying ref deletion for refs/heads/next To blah.git ! [remote rejected] next (deletion prohibited) error: failed to push some refs to 'blah.git I am using gitolite and cannot find any of this error message in the hooks. How can I disable this so that I can delete or rename this remote branch? When I run git branch -r -d origin/next, it appears to go away, but the next git pull brings it right back. Make sure in your gitolite config, you have the rewind flag on so instead of RW use RW+ . That will allow you