git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ddw_music <jamshark70@gmail.com>
To: git@vger.kernel.org
Subject: Re: (osx 10.4.11) can't push from linux to Apache on mac: can't access location
Date: Sat, 12 Jun 2010 23:35:11 -0700 (PDT)	[thread overview]
Message-ID: <1276410911244-5173593.post@n2.nabble.com> (raw)
In-Reply-To: <AANLkTim4U99KQ2zDfdSmMzbn1FqCqAPh_hKwITmQDX6H@mail.gmail.com>



Tay Ray Chuan wrote:
> 
> Where are you pushing to? Look at your <Location> again - you
> configured Apache to look out for '/git/kc/', not '/~dewdrop/git/kc/'.
> 

Ah... of course. Now I do get the directory listing of the repository on the
remote machine.

Still a problem pushing, though: the famous "cannot lock existing info/refs"
message. I see a reference on a Google group -- a problem/solution post* --
but that's inaccessible to me from mainland China. Likely to be something
simple, but I have actual work that I need to get back to at the moment :-)

* groups.google.com/group/.../0792d1750d764225

Thanks for further advice.
James
-- 
View this message in context: http://git.661346.n2.nabble.com/osx-10-4-11-can-t-push-from-linux-to-Apache-on-mac-can-t-access-location-tp5173157p5173593.html
Sent from the git mailing list archive at Nabble.com.

  reply	other threads:[~2010-06-13  7:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-13  0:48 (osx 10.4.11) can't push from linux to Apache on mac: can't access location ddw_music
2010-06-13  5:23 ` Tay Ray Chuan
2010-06-13  6:35   ` ddw_music [this message]
2010-06-13  7:20     ` Tay Ray Chuan
2010-06-13 10:28       ` ddw_music
2010-06-13 10:44         ` Jakub Narebski
2010-06-13 11:56           ` ddw_music
2010-06-13 12:38             ` Jakub Narebski
2010-06-17 22:26   ` mobi phil

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=1276410911244-5173593.post@n2.nabble.com \
    --to=jamshark70@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).