Re: [PATCH 2/4] doc: add verb in front of command to run

[Philip Oakley]

From: "Kristoffer Haugsbakk" 
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 
---
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 ') 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 

[PATCH 2/4] doc: add verb in front of command to run

[Kristoffer Haugsbakk]

Instead of using the command 'git clone' as a verb, use "run" as the
verb indicating the action of executing the command 'git clone'.

Signed-off-by: Kristoffer Haugsbakk 
---
 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
repository of the "project lead". The URL used for the
initial cloning is stored in the remote.origin.url
configuration variable.
-- 
2.11.0