git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tay Ray Chuan <rctay89@gmail.com>
To: Tarmigan Casebolt <tarmigan+git@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [PATCH v2] Smart-http documentation: add example of how to  execute from userdir
Date: Thu, 31 Dec 2009 10:18:09 +0800	[thread overview]
Message-ID: <be6fef0d0912301818o678976ebqa3e339dc1ff1f2e8@mail.gmail.com> (raw)
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:
> 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.

> +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

  reply	other threads:[~2009-12-31  2: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
2009-12-28  4:46     ` [PATCH v2] " Tarmigan Casebolt
2009-12-31  2:18       ` Tay Ray Chuan [this message]
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=be6fef0d0912301818o678976ebqa3e339dc1ff1f2e8@mail.gmail.com \
    --to=rctay89@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=spearce@spearce.org \
    --cc=tarmigan+git@gmail.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.
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).