Mihamina Rakotomandimby <mihamina@xxxxxx> writes: > I made several commits to a small local program. > When I list them with "git log" I see them. > > To publish my work, I choosed to sign in a forge (like github, google > code,...). I choosed forge.ocamlcore.org Note that you don't have to choose _one_ place. With distributed version control systems you can interact with many remote repositories (though only one would be called "origin" and would be the default repository). I for example push both to repo.or.cz and to GitHub. > With my account creation, the forge automatically created an empty GIT > repository. > > I clone it with: > > $ git clone git+ssh://rakotomandimby@xxxxxxxxxxxxxxxxxxx/gitroot/ocaml-crypt/ocaml-crypt.git > Initialized empty Git repository in /tmp/ocaml-crypt/ocaml-crypt/.git/ > warning: You appear to have cloned an empty repository. > > I am surprised the initialisation is not in /tmp/ocaml-crypt/ocaml-crypt.git/.git/ > as I pulled "ocaml-crypt.git". It is Git convention to use 'project/.git' for a working repository, which working area (checked out files) in 'project/', while using 'project.git' for name of _bare_ repository, i.e. without working directory. project/.git == project.git project/ [no workdir] > Anyway... > When add+commit a file into "/tmp/ocaml-crypt/ocaml-crypt/", > I get no errors, but when pushing: > > $ git push > No refs in common and none specified; doing nothing. > Perhaps you should specify a branch such as 'master'. > fatal: The remote end hung up unexpectedly > > I don't understand... The default Git behavior is to push *only* matching branches. With this workflow you must push a branch explicitly first time. What you need to do is to use $ git push --all to push all branches, or "git push origin HEAD" to push only current branch. This behavior is configurable, either via `push.default` config variable, or via `remote.origin.push`. HTH -- Jakub Narebski Poland ShadeHawk on #git -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html