From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: git@vger.kernel.org
Subject: [PATCH 5/6] manual: use 'URL' instead of 'url'.
Date: Tue, 9 Oct 2007 23:03:55 +0200 [thread overview]
Message-ID: <20071009210355.GG31317@ins.uni-bonn.de> (raw)
In-Reply-To: <20071009205755.GB31317@ins.uni-bonn.de>
Just for consistency, use the spelling URL everywhere.
---
Documentation/user-manual.txt | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index df482e6..38e35d8 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -1782,7 +1782,7 @@ $ git clone /path/to/repository
$ git pull /path/to/other/repository
-------------------------------------------------
-or an ssh url:
+or an ssh URL:
-------------------------------------------------
$ git clone ssh://yourhost/~you/repository
@@ -1843,7 +1843,7 @@ Exporting a git repository via the git protocol
This is the preferred method.
If someone else administers the server, they should tell you what
-directory to put the repository in, and what git:// url it will appear
+directory to put the repository in, and what git:// URL it will appear
at. You can then skip to the section
"<<pushing-changes-to-a-public-repository,Pushing changes to a public
repository>>", below.
@@ -1880,8 +1880,8 @@ $ chmod a+x hooks/post-update
gitlink:git-update-server-info[1], and the documentation
link:hooks.html[Hooks used by git].)
-Advertise the url of proj.git. Anybody else should then be able to
-clone or pull from that url, for example with a command line like:
+Advertise the URL of proj.git. Anybody else should then be able to
+clone or pull from that URL, for example with a command line like:
-------------------------------------------------
$ git clone http://yourserver.com/~you/proj.git
--
1.5.3.3.g34c6d
next prev parent reply other threads:[~2007-10-09 21:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 20:57 [PATCH 0/6] Some small documentation fixes Ralf Wildenhues
2007-10-09 21:00 ` [PATCH 1/6] Fix some typos, punctuation, missing words, minor markup Ralf Wildenhues
2007-10-09 21:01 ` [PATCH 2/6] Fix wording in push definition Ralf Wildenhues
2007-10-09 21:02 ` [PATCH 3/6] manual: Fix example finding commits referencing given content Ralf Wildenhues
2007-10-09 21:03 ` [PATCH 4/6] manual: add some markup Ralf Wildenhues
2007-10-09 21:03 ` Ralf Wildenhues [this message]
2007-10-09 21:05 ` [PATCH 0/6] manual: Fix or remove em dashes Ralf Wildenhues
2007-10-09 21:41 ` Thomas Adam
2007-10-09 21:52 ` Ralf Wildenhues
2007-10-09 22:02 ` Thomas Adam
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=20071009210355.GG31317@ins.uni-bonn.de \
--to=ralf.wildenhues@gmx.de \
--cc=git@vger.kernel.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).