From: Jakub Narebski <jnareb@gmail.com>
To: Mihamina Rakotomandimby <mihamina@bbs.mg>
Cc: git@vger.kernel.org
Subject: Re: help on importing
Date: Sun, 19 Jun 2011 08:23:16 -0700 (PDT) [thread overview]
Message-ID: <m3sjr5u9qg.fsf@localhost.localdomain> (raw)
In-Reply-To: <20110619180348.576ea06e.mihamina@bbs.mg>
Mihamina Rakotomandimby <mihamina@bbs.mg> 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@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]
> 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
prev parent reply other threads:[~2011-06-19 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-19 15:03 help on importing Mihamina Rakotomandimby
2011-06-19 15:23 ` Jakub Narebski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3sjr5u9qg.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=mihamina@bbs.mg \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.