On Monday 05 April 2010 21:09:21 lusha wang wrote: > When i use git push, there shows an error: > protocol error: expected sha/ref, got 'ERR > You can't push to git://github.com/freenet/fred-staging.git > Use g...@github.com:freenet/fred-staging.git'
You are trying to push to the main repository. You may not have commit rights, or if you do you've just checked it out from the wrong place. What you need to do is branch the main repository on github to get your own repo, and then push to that. You will need to do git remote add lusha [ url from github ], then do git push lusha, then send a pull request (github provides an easy way to do this, otherwise you can just email). Alternatively, get pushing rights, then do: git remote rm origin git remote add g...@github.com:freenet/fred-staging.git However, we are trying to move to a model where fewer people have pushing rights, as this results in fewer reverts, so it is better to branch it and then post a pull request. > > On Mon, Apr 5, 2010 at 7:04 AM, Ximin Luo <xl...@cam.ac.uk> wrote: > > > > Subject: conventional hashes and pull-request > > > > whoops, it looks like i lost track of what i was writing about.. > > > > lusha, you send a pull-request to fred-staging but there are no commits to > > pull > > in your personal branch http://github.com/lusha/fred-staging > > > > did you remember to "git push" after you did "git commit"? otherwise, the > > commits will only remain on your own hard drive, and not be uploaded > > ("pushed") > > to github.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Devl mailing list Devl@freenetproject.org http://osprey.vm.bytemark.co.uk/cgi-bin/mailman/listinfo/devl