| 1 |
<h1>FAQ</h1> |
| 2 |
|
| 3 |
<h3>I get "fatal: no matching remote head" when trying to clone a repository</h3> |
| 4 |
<p> |
| 5 |
Most likely the repository you're trying to clone is empty, and the error |
| 6 |
message is git's friendly way of telling you that. See below (or by clicking |
| 7 |
"more info" next to the repository's "push url") for info on how to push to it. |
| 8 |
</p> |
| 9 |
|
| 10 |
<hr /> |
| 11 |
|
| 12 |
<h3>How do I point my local Git repository at Gitorious?</h3> |
| 13 |
<p> |
| 14 |
Easiest way is to put something like the following in your <code>.git/config</code> |
| 15 |
file of the repository you wish to push: |
| 16 |
<pre> |
| 17 |
[remote "origin"] |
| 18 |
url = git@<%= GitoriousConfig['gitorious_host'] -%>:<em>project</em>/<em>repository.git</em> |
| 19 |
fetch = +refs/heads/*:refs/remotes/origin/* |
| 20 |
[branch "master"] |
| 21 |
remote = origin |
| 22 |
merge = refs/heads/master |
| 23 |
</pre> |
| 24 |
and then <code>git push origin master</code> to push the code to Gitorious. |
| 25 |
</p> |
| 26 |
<p> |
| 27 |
You can also just run "<code>git push git@<%= GitoriousConfig['gitorious_host'] -%>:tumbline/mainline.git</code>", or |
| 28 |
you can setup a remote by doing the following (add --fetch to the add call to |
| 29 |
get the config from above): |
| 30 |
<pre> |
| 31 |
git remote add origin git@<%= GitoriousConfig['gitorious_host'] -%>:<em>project</em>/<em>repository.git</em> |
| 32 |
# to push the master branch to the origin remote we added above: |
| 33 |
git push origin master |
| 34 |
# after that you can just do: |
| 35 |
git push |
| 36 |
</pre> |
| 37 |
</p> |
| 38 |
|
| 39 |
<hr /> |
| 40 |
|
| 41 |
<h3>Why is my email displayed?</h3> |
| 42 |
<p> |
| 43 |
The email you used to signup with Gitorious is displayed to other users, so that they |
| 44 |
can contact you about your projects if they need to. We do however take light |
| 45 |
measures against crawlers by not displaying your email in completely plain text. <br /> |
| 46 |
But just to be clear: we won't sell or use any information you give to |
| 47 |
<%= GitoriousConfig['gitorious_host'] -%> against you or anyone else for financial and/or personal gains. |
| 48 |
</p> |
| 49 |
|
| 50 |
<hr /> |
| 51 |
|
| 52 |
<h3>Why do I need to upload my public SSH key?</h3> |
| 53 |
<p> |
| 54 |
When you push to a Git repository, your public key is how we authenticate |
| 55 |
you and check if have the permissions required to do a commit to a given repository |
| 56 |
</p> |
| 57 |
|
| 58 |
<hr /> |
| 59 |
|
| 60 |
<h3>What version of Git is Gitorious running?</h3> |
| 61 |
<p> |
| 62 |
<code>git version 1.5.4.4</code> |
| 63 |
</p> |
| 64 |
|
| 65 |
<% content_for :sidebar do -%> |
| 66 |
<ul class="links"> |
| 67 |
<li><%= link_to "About", about_path(:anchor => "about") -%></li> |
| 68 |
<li><%= link_to "Contact", about_path(:anchor => "contact") -%></li> |
| 69 |
<li><%= link_to "FAQ", faq_path -%></li> |
| 70 |
</ul> |
| 71 |
<% end -%> |
