On Tue, 27 Aug 2013 01:16:49 -0700 (PDT)
Володимир Кулик <cdrwvova1...@gmail.com> wrote:

> parf@parf:~/work$ git push work
> FATAL: W any frontend.epass/parfymer parfymer DENIED by fallthru
> (or you mis-spelled the reponame)
> fatal: The remote end hung up unexpectedly

I suspect you're confusing "named remote repositories" (or simply "named
remotes") which are objects in the configuration of your local Git
repository with remote repositories existing on another machine which
hosts them.

Your local Git only ever accesses Git repositories on another machine
using their URLs; "user@host/path/to/the/repository" is an example of
such an URL (implying the SSH transport is used for communicating with
that remote machine).

Note that the URL you have used, "gitolite@IP_ADDRESS", does not include
any name of an actual repository on the remote host, so it has no sense
at all. To get a better idea about this, read the "GIT URLS" section of
the git-push manual page [1], and you will see that the path to the
repository (on the remote machine) is not an optional part of an URL.
That's why Git told you your URL did not look like a valid repository
URL when you tried to use it in your `git remote add ...` call.

Another thing you have to understand, that these "named remote
repositories" (which are managed by the `git remote` command) is just a
matter of convenience which
1) saves you from typing full URL each time you want to access a
   repository;
2) keeps "bookmarks" on the state of the branches of each named remote
   repository when you do `git fetch` on them -- in the form of the
   so-called "remote branches" (these "origin/master" etc).

The final facet of this "puzzle" is that, it appears, Git repositories
on your remote machines are managed by a special front-end tool called
`gitolite` [2].  It might be set up in a number of different ways but
*usually* it makes the repositories it hosts available without
specifying actual pathnames to them in their approptiate URLs, that is,
a repository "foobar" is usually accessed by the url like
"gitolite@hostname/foobar" or "gitolite@hostname/foobar.git".

So, I'd try to go like this.

First, inspect the list of named remotes you have by running
`git remote` or `git remote -v`.

If you have a remote named "frontend.epass", call

git remote set-url frontend.epass gitolite@hostname/frontend.epass

to update the repository's URL.

If you do not have this repository yet, call

git remote add frontend.epass gitolite@hostname/frontend.epass

1. https://www.kernel.org/pub/software/scm/git/docs/git-push.html
2. https://github.com/sitaramc/gitolite

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to