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: Sun, 13 Jun 2010 03:28:56 -0700 (PDT) [thread overview]
Message-ID: <1276424936869-5173934.post@n2.nabble.com> (raw)
In-Reply-To: <AANLkTilIGhEXlhEbAAXIU-_1Qg8AJoCalkilWGCzIP1m@mail.gmail.com>
Tay Ray Chuan wrote:
>
> I vaguely remember encountering this. Use a dav client, like cadaver,
> to manually release the lock.
>
> $ cadaver http://yourserver/git/kc/
> > discover info/refs
>
> <bla bla: look for the lock token>
> > unlock <token>
>
I do appreciate the help... unfortunately, cadaver reports no locks but the
error persists...
For my purposes, I think I can use git-daemon. It's approaching the point
where it will not be worth dealing with the Apache layer. Unless there is a
simple solution, the HTTP approach seems to be adding complexity without
much benefit.
If anyone out there knows of a straightforward way to set this up, I'm eager
to hear it. (By "straightforward," I mean I'm out of time to fiddle around
with it much more.) If there is no straightforward way, git-daemon it will
be for me.
Thanks.
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-tp5173157p5173934.html
Sent from the git mailing list archive at Nabble.com.
next prev parent reply other threads:[~2010-06-13 10:29 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
2010-06-13 7:20 ` Tay Ray Chuan
2010-06-13 10:28 ` ddw_music [this message]
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=1276424936869-5173934.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).