git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] Update setup-git-server-over-http.txt based on my experience.
Date: Thu, 3 Apr 2008 19:12:46 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LSU.1.00.0804031905410.4008@racer.site> (raw)
In-Reply-To: <1207241902-4667-1-git-send-email-Matthieu.Moy@imag.fr>

Hi,

I don't like the commit subject.  At all.

On Thu, 3 Apr 2008, Matthieu Moy wrote:

> -- have git installed at the server _and_ client
> +- have git installed on the client, and preferably on the server

How do you want to initialise the repository on the server, then?  (IOW 
you should mention here that you need a WebDAV client on the client if you 
do not have Git on the server, and that it is way more fiddly.)

> -In effect, this probably means you're going to be root.
> +In effect, this probably means you're going to be root, or that you're
> +using a preconfigured WebDAV server.

Either you strike "probably" or you skip what you added.

> @@ -169,7 +170,8 @@ On Debian:
>  
>     Most tests should pass.
>  
> -A command line tool to test WebDAV is cadaver.
> +A command line tool to test WebDAV is cadaver. If you prefer GUIs,
> +konqueror can open WebDAV URLs as "webdav://..." or "webdavs://...".

What do you do if you have MacOSX, or Windows?

> @@ -179,8 +181,10 @@ http://<servername>/my-new-repo.git [x] Open as webfolder -> login .
>  Step 3: setup the client
>  ------------------------
>  
> -Make sure that you have HTTP support, i.e. your git was built with curl.
> -The easiest way to check is to look for the executable 'git-http-push'.
> +Make sure that you have HTTP support, i.e. your git was built with
> +curl (and a recent enough version).

Say what version.  Otherwise this comment will soon be very, very stale.

> +The easiest way to check is to +look for the executable 
> 'git-http-push'. The command "git http-push" +with no argument should 
> display a usage message.

My search revealed that http-push was in Git since tags/v0.99.9e^2~9^2~4.  
Which is not recent at all.

> @@ -212,6 +216,10 @@ It is important to put the last '/'; Without it, the server will send
>  a redirect which git-http-push does not (yet) understand, and git-http-push
>  will repeat the request infinitely.
>  
> +Also note that the URL should point to the git repository itself, that
> +is, to the '.git/' directory and not the working tree in case the
> +repository is non-bare.

It makes no sense to describe the case of a non-bare repository.

Especially with those many threads on the list these days, describing the 
mess people got into by pushing into non-bare repositories!

> @@ -224,6 +232,13 @@ This pushes branch 'master' (which is assumed to be the branch you
>  want to export) to repository called 'upload', which we previously
>  defined with git-config.
>  
> +Using a proxy:
> +--------------
> +
> +If you have to access the WebDAV server from behind an HTTP(S) proxy,
> +set the variable 'all_proxy' to 'http://proxy-host.com:port', or
> +'http://login-on-proxy:passwd-on-proxy@proxy-host.com:port'. See 'man
> +curl' for details.

You only need http_proxy.

Ciao,
Dscho

  reply	other threads:[~2008-04-03 18:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03 16:58 [PATCH] Update setup-git-server-over-http.txt based on my experience Matthieu Moy
2008-04-03 17:12 ` Johannes Schindelin [this message]
2008-04-03 20:56   ` Matthieu Moy
2008-04-03 20:28     ` Johannes Schindelin

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LSU.1.00.0804031905410.4008@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=Matthieu.Moy@imag.fr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).