Re: [PATCH v2] Smart-http documentation: add example of how to execute from userdir

From: Tay Ray Chuan <rctay89@gmail.com>
Date: Dec 31, 2009, 02:18 UTC
Message-ID: <be6fef0d0912301818o678976ebqa3e339dc1ff1f2e8@mail.gmail.com>
In-Reply-To: <1261975612-67101-1-git-send-email-tarmigan+git@gmail.com>

Hi,

On Mon, Dec 28, 2009 at 12:46 PM, Tarmigan Casebolt <tarmigan+git@gmail.com> wrote:

Show 5 quoted lines

> Looking at the
>        s/update/updates/
> suggestion again, I decided not to make that change because I think
> the original is grammical even if a little bit awkward.  The first
> 'updates' is the noun, so the verb should be 'update' without an 's'.

Indeed.

> I also tried rephrasing that sentence completely, but did not end up
> with something better. ?Suggestions welcome.

My attempt is found below.

> +In the following example, a repository at

I was thinking s/a repository at/the repository/.

> +'/home/$username/devel/foo/bar.git' will be accessible at
> +'http://$hostname/\~$username/cgi-bin/git/foo/bar.git'

You left out a full-stop for this sentence.

Show 8 quoted lines

> +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 named 'git' that points
> +       from the cgi directory to the 'git-http-backend' executable in
> +       libexec.  The advantage of the symbolic link is that any updates
> +       to the installed version of 'git-http-backend' also update the
> +       version that is run in the userdir.

We could try

  The advantage is that this symbolic link always points to the latest
  installed version; one does not have to make any changes to the
  symbolic link when the installed 'git-http-backend' is updated.

I thought the corollary (after the ';') was a bit long-winded, but it explains the advantage more clearly.

-- 
Cheers,
Ray Chuan