Git development
 help / color / mirror / Atom feed
From: "Philip Oakley" <philipoakley@iee.org>
To: "Kristoffer Haugsbakk" <kristoffer.haugsbakk@gmail.com>,
	<git@vger.kernel.org>
Cc: "Kristoffer Haugsbakk" <kristoffer.haugsbakk@gmail.com>
Subject: Re: [PATCH 2/4] doc: add verb in front of command to run
Date: Sat, 10 Dec 2016 20:48:37 -0000	[thread overview]
Message-ID: <2C16DAFED0D94B28AF9CE7F8BBA122F0@PhilipOakley> (raw)
In-Reply-To: 20161209155112.2112-3-kristoffer.haugsbakk@gmail.com

From: "Kristoffer Haugsbakk" <kristoffer.haugsbakk@gmail.com>
Sent: Friday, December 09, 2016 3:51 PM
> Instead of using the command 'git clone' as a verb, use "run" as the
> verb indicating the action of executing the command 'git clone'.

I would expect 'cloning' as the commonly in use verb here, with the command 
then quoted.

>
> Signed-off-by: Kristoffer Haugsbakk <kristoffer.haugsbakk@gmail.com>
> ---
> Documentation/gitcore-tutorial.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/gitcore-tutorial.txt 
> b/Documentation/gitcore-tutorial.txt
> index 6c434aff3..72ed90ca3 100644
> --- a/Documentation/gitcore-tutorial.txt
> +++ b/Documentation/gitcore-tutorial.txt
> @@ -1478,7 +1478,7 @@ You can repack this private repository whenever you 
> feel like.
> A recommended work cycle for a "subsystem maintainer" who works
> on that project and has an own "public repository" goes like this:
>
> -1. Prepare your work repository, by 'git clone' the public
> +1. Prepare your work repository, by running 'git clone' on the public

Perhaps ?
... by cloning ('git clone <URL>') the public

The full command is shown using the same terminology as the following line.

>    repository of the "project lead". The URL used for the
>    initial cloning is stored in the remote.origin.url
>    configuration variable.
> -- 
> 2.11.0
>
>
--
Philip 


  reply	other threads:[~2016-12-10 20:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-09 15:51 [PATCH 0/4] doc: fixes to gitcore-tutorial.txt Kristoffer Haugsbakk
2016-12-09 15:51 ` [PATCH 1/4] doc: add articles (grammar) Kristoffer Haugsbakk
2016-12-10 20:28   ` Philip Oakley
2016-12-13 13:05     ` Kristoffer Haugsbakk
2016-12-13 18:11       ` Junio C Hamano
2016-12-13 21:34         ` Kristoffer Haugsbakk
2016-12-09 15:51 ` [PATCH 2/4] doc: add verb in front of command to run Kristoffer Haugsbakk
2016-12-10 20:48   ` Philip Oakley [this message]
2016-12-09 15:51 ` [PATCH 3/4] doc: make the intent of sentence clearer Kristoffer Haugsbakk
2016-12-10 20:52   ` Philip Oakley
2016-12-13 13:23     ` Kristoffer Haugsbakk
2016-12-09 15:51 ` [PATCH 4/4] doc: omit needless "for" Kristoffer Haugsbakk
2016-12-11 13:04   ` Philip Oakley
2016-12-11 14:08     ` Philip Oakley
2016-12-09 23:13 ` [PATCH 0/4] doc: fixes to gitcore-tutorial.txt Junio C Hamano

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=2C16DAFED0D94B28AF9CE7F8BBA122F0@PhilipOakley \
    --to=philipoakley@iee.org \
    --cc=git@vger.kernel.org \
    --cc=kristoffer.haugsbakk@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