git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: help on importing

From
Jakub Narebski <jnareb@gmail.com>
Date
Jun 19, 2011, 15:23 UTC
Message-ID
<m3sjr5u9qg.fsf@localhost.localdomain>
In-Reply-To
<20110619180348.576ea06e.mihamina@bbs.mg>
Mihamina Rakotomandimby <mihamina@bbs.mg> writes:
Show 5 quoted lines
> 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.
 
Show 11 quoted lines
> With my account creation, the forge automatically created an empty GIT
> repository.
> 
> I clone it with:
>
>   $ git clone git+ssh://rakotomandimby@forge.ocamlcore.org/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]
Show 10 quoted lines
> 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
Previous: Mihamina Rakotomandimby
Message 2 of 2 in “help on importing”
  1. Mihamina RakotomandimbyJun 19, 2011
  2. Jakub NarebskiJun 19, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.