From: Jon Loeliger <jdl@freescale.com>
To: Anatoly Yakovenko <aeyakovenko@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Mike Hommey <mh@glandium.org>,
git@vger.kernel.org
Subject: Re: cant get git to work over http
Date: Tue, 19 Feb 2008 14:05:37 -0600 [thread overview]
Message-ID: <47BB3691.9040809@freescale.com> (raw)
In-Reply-To: <e26d18e40802191153w691ac5fcl3fa972ca6503b9fb@mail.gmail.com>
Anatoly Yakovenko wrote:
>
> $ git-clone ssh://aeyakovenko@localhost/var/www/localhost/htdocs/git/repo/ repo
> Initialized empty Git repository in /home/aeyakovenko/projects/repo/repo/.git/
> aeyakovenko@localhost's password:
> Receiving objects: 100% (3/3), done.
> remote: Counting objects: 3, done.
> remote: Total 3 (delta 0), reused 0 (delta 0)
>
> but for the life of me i cant do this:
>
> $ git-clone http://aeyakovenko@localhost/var/www/localhost/htdocs/git/repo/ repo
> Initialized empty Git repository in /home/aeyakovenko/projects/repo/.git/
> Cannot get remote repository information.
> Perhaps git-update-server-info needs to be run there?
Ponder the Doc Root for an HTTP request. Remember that your httpd
will likely be striping or rewriting that base directory path and
so it won't be needed on your git http:// requests.
Since my repository was outside of the basic Doc Root, and I wanted
to present similar path names to both git: and http: protocols, I
ended up rewriting some URL paths. Also, if you have some form of
virtual hosting going on, you might need to do a virtualization
rewriting using --interpolated-path=pathtemplate.
HTH,
jdl
next prev parent reply other threads:[~2008-02-19 20:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 0:49 cant get git to work over http Anatoly Yakovenko
2008-02-19 6:39 ` Mike Hommey
2008-02-19 7:09 ` Anatoly Yakovenko
2008-02-19 9:39 ` Mike Hommey
2008-02-19 11:18 ` Johannes Schindelin
2008-02-19 18:19 ` Anatoly Yakovenko
2008-02-19 18:24 ` Jon Loeliger
2008-02-19 19:06 ` Anatoly Yakovenko
2008-02-19 19:19 ` Johannes Schindelin
2008-02-19 19:27 ` Anatoly Yakovenko
2008-02-19 19:41 ` Johannes Schindelin
2008-02-19 19:53 ` Anatoly Yakovenko
2008-02-19 19:57 ` Johannes Schindelin
2008-02-19 19:57 ` Jeff King
2008-02-19 20:05 ` Jon Loeliger [this message]
2008-02-19 21:05 ` Anatoly Yakovenko
2008-02-19 21:55 ` Jon Loeliger
2008-02-19 21:59 ` Anatoly Yakovenko
2008-02-19 22:13 ` Anatoly Yakovenko
2008-02-19 22:20 ` Johannes Schindelin
2008-02-20 13:46 ` Anton Gladkov
2008-02-20 10:39 ` Robert Haines
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=47BB3691.9040809@freescale.com \
--to=jdl@freescale.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=aeyakovenko@gmail.com \
--cc=git@vger.kernel.org \
--cc=mh@glandium.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).