From: Neal Kreitzinger <nkreitzinger@gmail.com>
To: Jerome Yanga <jerome.yanga@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git push from client is not updating files on server
Date: Tue, 06 Mar 2012 17:32:56 -0600 [thread overview]
Message-ID: <4F569EA8.4050907@gmail.com> (raw)
In-Reply-To: <CAC0z1F87ORZQmrZeMGo2suV1fAt-5mAwwpkkV3ZTx0US3AjM8Q@mail.gmail.com>
On 3/6/2012 5:07 PM, Jerome Yanga wrote:
> Is there a way to make git write to the working directory of the
> central public server?
>
In your original post you stated:
> From the git client server, I can successfully clone projects in from
> the central public Git server using the command below.
>
> git clone
http://<hostname_of_central_public_git_server>/<Project_name>.git
".git" extension implies "bare" repo. A bare repo has _no_ working
tree. Is the repo in question bare or non-bare? If you are not sure,
then cd to the central-repo-dir (ie., the <Project_name>.git you cloned
_from_ in your example above) and run "git config -l |grep bare". If it
says "core.bare=true" then it is a bare repo.
v/r,
neal
next prev parent reply other threads:[~2012-03-06 23:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 16:52 git push from client is not updating files on server Jerome Yanga
2012-03-06 17:46 ` Ben Tebulin
2012-03-06 19:35 ` Junio C Hamano
[not found] ` <CAC0z1F-Eg2DOLvd3aA5XCoEJjj1jC=VWVkTA+uc24=18h3pN7g@mail.gmail.com>
2012-03-06 20:37 ` Junio C Hamano
2012-03-06 21:12 ` Neal Kreitzinger
2012-03-06 21:21 ` Neal Kreitzinger
[not found] ` <CAC0z1F_eyMo4D8E2j15dOFhp-6tZ_ixacB6XcKfNpJategcsXQ@mail.gmail.com>
[not found] ` <CAC0z1F_LYRkReO1qqcjkWy6Vb3E0_oNo-0kSf15nGfQFAtXpdg@mail.gmail.com>
2012-03-06 23:07 ` Jerome Yanga
2012-03-06 23:32 ` Neal Kreitzinger [this message]
2012-03-07 0:28 ` Jerome Yanga
2012-03-07 1:11 ` Neal Kreitzinger
2012-03-07 2:23 ` Junio C Hamano
2012-03-07 2:34 ` Neal Kreitzinger
2012-03-07 11:04 ` Holger Hellmuth
2012-03-07 15:43 ` Jerome Yanga
2012-03-30 18:23 ` Jerome Yanga
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=4F569EA8.4050907@gmail.com \
--to=nkreitzinger@gmail.com \
--cc=git@vger.kernel.org \
--cc=jerome.yanga@gmail.com \
/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.