From: Tarmigan <tarmigan+git@gmail.com>
To: Tay Ray Chuan <rctay89@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [PATCH] Smart-http documentation: add example of how to execute from userdir
Date: Sun, 27 Dec 2009 23:18:42 -0500 [thread overview]
Message-ID: <905315640912272018r1282394fh62d37b5c9e91a234@mail.gmail.com> (raw)
In-Reply-To: <be6fef0d0912261919m7b175c4fh532ad05a713d86c7@mail.gmail.com>
On Sat, Dec 26, 2009 at 10:19 PM, Tay Ray Chuan <rctay89@gmail.com> wrote:
>> -All of the following examples map 'http://$hostname/git/foo/bar.git'
>> -to '/var/www/git/foo/bar.git'.
>> +Unless otherwise noted, the following examples map
>> +'http://$hostname/git/foo/bar.git' to '/var/www/git/foo/bar.git'.
>
> This rephrase seems to be unrelated (to providing an example of
> serving smart http).
I think this change is related because previously all the examples
provided the same mapping. With the new example with a different
mapping, the "_All_ of the following" is no longer true.
>> @@ -144,6 +144,42 @@ ScriptAliasMatch \
>> ScriptAlias /git/ /var/www/cgi-bin/gitweb.cgi/
>> ----------------------------------------------------------------
>>
>> +In the following example, a repository at
>> +'/home/$username/devel/foo/bar.git' will be accessible at
>> +'http://$hostname/\~$username/cgi-bin/git/foo/bar.git'
>> +
>> +From UserDir on Apache 2.x::
>> + One way to configure 'git-http-backend' to execute and serve
>> + from a user directory (for example, on a shared hosting
>> + provider), is to have a symbolic link that points from the cgi
>> + directory to the 'git-http-backend' executable in libexec. The
>> + advantage of the symblic link is that any updates to the
>
> s/symblic/symbolic
> s/update/updates/.
Thanks.
> At this point, the user dealing with the "easy" case (ie. the user
> just symlinks the shared git installation and doesn't have to create
> symlinks in his own home directory) should have enough configuration
> details without having to read any further. So, you could tell the
> user about the symlinks to create and the configuration lines in
> .htaccess.
>
> It might also be a good idea to start a new paragraph for the "hard"
> case, for better readability.
OK, these suggestions sound good to me. I'll send out an updated patch shortly.
Thanks,
Tarmigan
next prev parent reply other threads:[~2009-12-28 4:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-26 17:07 [PATCH] Smart-http documentation: add example of how to execute from userdir Tarmigan Casebolt
2009-12-27 3:19 ` Tay Ray Chuan
2009-12-28 4:18 ` Tarmigan [this message]
2009-12-28 4:46 ` [PATCH v2] " Tarmigan Casebolt
2009-12-31 2:18 ` Tay Ray Chuan
2010-01-02 21:18 ` [PATCH v3] " Tarmigan Casebolt
2010-01-03 2:11 ` Tay Ray Chuan
2010-01-03 8:34 ` Junio C Hamano
2010-01-04 14:06 ` Shawn O. Pearce
2010-01-05 7:59 ` Tarmigan
2010-01-05 7:59 ` [PATCH v4] " Tarmigan Casebolt
2010-01-05 8:23 ` Junio C Hamano
2009-12-27 21:15 ` [PATCH] " Shawn O. Pearce
2009-12-28 4:06 ` Tarmigan
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=905315640912272018r1282394fh62d37b5c9e91a234@mail.gmail.com \
--to=tarmigan+git@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rctay89@gmail.com \
--cc=spearce@spearce.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).