On Wed, Oct 16, 2013 at 09:10:12PM +0400, Konstantin Khomoutov wrote: > On Wed, 16 Oct 2013 13:16:23 +0200 > Magnus Therning <mag...@therning.org> wrote: > > > > git 1.8.4 > > > output of 'git remote -v' > > > origin user@gitservre:/path/to/dir/projectd.git (fetch) > > > origin user@gitservre:/path/to/dir/projectd.git (push) > > > > > > I saw now that you send me another email, and I tried 'git push > > > origin master' and it start working. > > > Now 'git push' also work. I don't know what cause the problem. > > > Maybe something on the server? > > > > > > If you have any idea I will be happy to know. > > > > Most likely you cloned from a completely empty repo, in which case the > > `master` branch doesn't exist. What you did was tell git *exactly* > > where to push, so it creates the master branch on the remote. > > I would say it's rather "what to push", not "where": a call > > git push origin master > > implies we intend to push local ref "master" to a same-named remote > ref, and create it there if it does not exist yet.
So, to be nitpicky you are actually arguing for saying that it's *both* "what to push" and "where to push" ;) /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: mag...@therning.org jabber: mag...@therning.org twitter: magthe http://therning.org/magnus But whereas I previously held for Java a cordial dislike borne of having only a cursory notion of how it worked, now my dislike for the language can no longer be called at all "cordial", for familiarity has bred contempt. -- tom Christiansen
Description: PGP signature