All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Uemlianin <ivan@llaisdy.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: git pull works remotely but not locally
Date: Thu, 27 May 2010 14:35:07 +0100	[thread overview]
Message-ID: <4BFE750B.5030007@llaisdy.com> (raw)

Dear All

I have just set up my first git repository, and I'm trying things out 
before using it for real.  To start with I'm using a centralised 
workflow with the main repos on a server, and workers checking work out 
and in.  I'm using the smart http backend.  I can contact the repos 
remotely via http or locally using the filesystem.  However, git pull is 
not working in the local case.  Please can someone offer help with (a) 
file permissions, and (b) difference between git pull, and git fetch; 
git merge (which works):

The basics seem to be working OK remotely: ie contacting the server over 
http:

         git clone http://username@12.34.56.78/git/projectname.git

What I mean is push and pull are working.

When working on the server itself I'm using

         git clone  /var/www/git/projectname.git

Most things seem to work the same, but git pull does not work:

         $ git pull
         fatal: cannot exec 'git-pull': Permission denied

fetch followed by merge seems to have the desired effect, e.g.:

    $ git fetch
    remote: Counting objects: 5, done.
    remote: Compressing objects: 100% (2/2), done.
    remote: Total 3 (delta 1), reused 0 (delta 0)
    Unpacking objects: 100% (3/3), done.
     From /var/www/git/projectname
        6b40c1f..4ffb389  master     -> origin/master

    $ git merge origin
    Updating 6b40c1f..4ffb389
    Fast-forward
      notes.txt |    1 +
      1 files changed, 1 insertions(+), 0 deletions(-)


So, my questions are:

(a)  Why isn't git pull working in the second case?  What permissions am 
I missing?
(b)  Does git fetch; git merge origin do the same thing as git pull?

With thanks and best wishes

Ivan


-- 
============================================================
Ivan A. Uemlianin
Speech Technology Research and Development

                     ivan@llaisdy.com
                      www.llaisdy.com
                          llaisdy.wordpress.com
                      www.linkedin.com/in/ivanuemlianin

     "Froh, froh! Wie seine Sonnen, seine Sonnen fliegen"
                      (Schiller, Beethoven)
============================================================

             reply	other threads:[~2010-05-27 13:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27 13:35 Ivan Uemlianin [this message]
2010-05-27 14:20 ` git pull works remotely but not locally Ramkumar Ramachandra
2010-05-27 14:37   ` Ivan Uemlianin
2010-05-27 14:47     ` Sverre Rabbelier
2010-05-27 15:07       ` Ivan Uemlianin
2010-05-27 15:15         ` Jeff King
2010-05-27 15:21           ` Ivan Uemlianin
2010-05-27 15:28             ` Johannes Sixt
2010-05-27 15:37               ` Ivan Uemlianin
2010-05-27 15:38             ` Jeff King
2010-05-27 16:21               ` Ivan Uemlianin
2010-05-27 16:57                 ` Ilari Liusvaara
2010-05-27 15:15         ` Ramkumar Ramachandra
2010-05-27 15:36           ` Ivan Uemlianin
2010-05-27 19:53             ` Johannes Sixt
2010-05-28  8:24               ` Ivan Uemlianin
2010-05-27 14:50     ` Ramkumar Ramachandra

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=4BFE750B.5030007@llaisdy.com \
    --to=ivan@llaisdy.com \
    --cc=git@vger.kernel.org \
    /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.