@matheusbsbs / matheus-bagliano / commits / 7706294ec9

doc: uniformize <URL> placeholders' case

URL being an acronym, it deserves to be kept uppercase. Signed-off-by: Jean-Noël Avila <jn.avila@free.fr> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Jean-Noël Avila committed Nov 6, 2021 at 19:48 UTC 7706294ec94ab9f9b864a8451ac089f15d18a254
8 files changed +20 -20
Documentation/git-http-fetch.txt
+1 -1
@@ -9,7 +9,7 @@ git-http-fetch - Download from a remote Git repository via HTTP
9 SYNOPSIS
10 --------
11 [verse]
12 -'git http-fetch' [-c] [-t] [-a] [-d] [-v] [-w <filename>] [--recover] [--stdin | --packfile=<hash> | <commit>] <url>
12 +'git http-fetch' [-c] [-t] [-a] [-d] [-v] [-w <filename>] [--recover] [--stdin | --packfile=<hash> | <commit>] <URL>
13
14 DESCRIPTION
15 -----------
Documentation/git-http-push.txt
+1 -1
@@ -9,7 +9,7 @@ git-http-push - Push objects over HTTP/DAV to another repository
9 SYNOPSIS
10 --------
11 [verse]
12 -'git http-push' [--all] [--dry-run] [--force] [--verbose] <url> <ref> [<ref>...]
12 +'git http-push' [--all] [--dry-run] [--force] [--verbose] <URL> <ref> [<ref>...]
13
14 DESCRIPTION
15 -----------
Documentation/git-remote.txt
+4 -4
@@ -10,7 +10,7 @@ SYNOPSIS
10 --------
11 [verse]
12 'git remote' [-v | --verbose]
13 -'git remote add' [-t <branch>] [-m <master>] [-f] [--[no-]tags] [--mirror=(fetch|push)] <name> <url>
13 +'git remote add' [-t <branch>] [-m <master>] [-f] [--[no-]tags] [--mirror=(fetch|push)] <name> <URL>
14 'git remote rename' <old> <new>
15 'git remote remove' <name>
16 'git remote set-head' <name> (-a | --auto | -d | --delete | <branch>)
@@ -18,7 +18,7 @@ SYNOPSIS
18 'git remote get-url' [--push] [--all] <name>
19 'git remote set-url' [--push] <name> <newurl> [<oldurl>]
20 'git remote set-url --add' [--push] <name> <newurl>
21 -'git remote set-url --delete' [--push] <name> <url>
21 +'git remote set-url --delete' [--push] <name> <URL>
22 'git remote' [-v | --verbose] 'show' [-n] <name>...
23 'git remote prune' [-n | --dry-run] <name>...
24 'git remote' [-v | --verbose] 'update' [-p | --prune] [(<group> | <remote>)...]
@@ -47,7 +47,7 @@ subcommands are available to perform operations on the remotes.
47 'add'::
48
49 Add a remote named <name> for the repository at
50 -<url>. The command `git fetch <name>` can then be used to create and
50 +<URL>. The command `git fetch <name>` can then be used to create and
51 update remote-tracking branches <name>/<branch>.
52 +
53 With `-f` option, `git fetch <name>` is run immediately after
@@ -152,7 +152,7 @@ With `--push`, push URLs are manipulated instead of fetch URLs.
152 With `--add`, instead of changing existing URLs, new URL is added.
153 +
154 With `--delete`, instead of changing existing URLs, all URLs matching
155 -regex <url> are deleted for remote <name>. Trying to delete all
155 +regex <URL> are deleted for remote <name>. Trying to delete all
156 non-push URLs is an error.
157 +
158 Note that the push URL and the fetch URL, even though they can
Documentation/git-request-pull.txt
+4 -4
@@ -8,7 +8,7 @@ git-request-pull - Generates a summary of pending changes
8 SYNOPSIS
9 --------
10 [verse]
11 -'git request-pull' [-p] <start> <url> [<end>]
11 +'git request-pull' [-p] <start> <URL> [<end>]
12
13 DESCRIPTION
14 -----------
@@ -21,7 +21,7 @@ the changes and indicates from where they can be pulled.
21 The upstream project is expected to have the commit named by
22 `<start>` and the output asks it to integrate the changes you made
23 since that commit, up to the commit named by `<end>`, by visiting
24 -the repository named by `<url>`.
24 +the repository named by `<URL>`.
25
26
27 OPTIONS
@@ -33,14 +33,14 @@ OPTIONS
33 Commit to start at. This names a commit that is already in
34 the upstream history.
35
36 -<url>::
36 +<URL>::
37 The repository URL to be pulled from.
38
39 <end>::
40 Commit to end at (defaults to HEAD). This names the commit
41 at the tip of the history you are asking to be pulled.
42 +
43 -When the repository named by `<url>` has the commit at a tip of a
43 +When the repository named by `<URL>` has the commit at a tip of a
44 ref that is different from the ref you have locally, you can use the
45 `<local>:<remote>` syntax, to have its local name, a colon `:`, and
46 its remote name.
Documentation/gitcredentials.txt
+2 -2
@@ -132,7 +132,7 @@ because the hostnames differ. Nor would it match `foo.example.com`; Git
132 compares hostnames exactly, without considering whether two hosts are part of
133 the same domain. Likewise, a config entry for `http://example.com` would not
134 match: Git compares the protocols exactly. However, you may use wildcards in
135 -the domain name and other pattern matching techniques as with the `http.<url>.*`
135 +the domain name and other pattern matching techniques as with the `http.<URL>.*`
136 options.
137
138 If the "pattern" URL does include a path component, then this too must match
@@ -147,7 +147,7 @@ CONFIGURATION OPTIONS
147
148 Options for a credential context can be configured either in
149 `credential.*` (which applies to all credentials), or
150 -`credential.<url>.*`, where <url> matches the context as described
150 +`credential.<URL>.*`, where <URL> matches the context as described
151 above.
152
153 The following options are available in either location:
Documentation/gitsubmodules.txt
+1 -1
@@ -226,7 +226,7 @@ Workflow for a third party library
226 ----------------------------------
227
228 # Add a submodule
229 - git submodule add <url> <path>
229 + git submodule add <URL> <path>
230
231 # Occasionally update the submodule to a new version:
232 git -C <path> checkout <new version>
Documentation/gitworkflows.txt
+3 -3
@@ -394,7 +394,7 @@ request to do so by mail. Such a request looks like
394
395 -------------------------------------
396 Please pull from
397 - <url> <branch>
397 + <URL> <branch>
398 -------------------------------------
399
400 In that case, 'git pull' can do the fetch and merge in one go, as
@@ -403,7 +403,7 @@ follows.
403 .Push/pull: Merging remote topics
404 [caption="Recipe: "]
405 =====================================
406 -`git pull <url> <branch>`
406 +`git pull <URL> <branch>`
407 =====================================
408
409 Occasionally, the maintainer may get merge conflicts when they try to
@@ -440,7 +440,7 @@ merge because you cannot format-patch merges):
440 .format-patch/am: Keeping topics up to date
441 [caption="Recipe: "]
442 =====================================
443 -`git pull --rebase <url> <branch>`
443 +`git pull --rebase <URL> <branch>`
444 =====================================
445
446 You can then fix the conflicts during the rebase. Presumably you have
Documentation/urls-remotes.txt
+4 -4
@@ -26,14 +26,14 @@ config file would appear like this:
26
27 ------------
28 [remote "<name>"]
29 - url = <url>
29 + url = <URL>
30 pushurl = <pushurl>
31 push = <refspec>
32 fetch = <refspec>
33 ------------
34
35 The `<pushurl>` is used for pushes only. It is optional and defaults
36 -to `<url>`.
36 +to `<URL>`.
37
38 Named file in `$GIT_DIR/remotes`
39 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -67,10 +67,10 @@ This file should have the following format:
67
68
69 ------------
70 - <url>#<head>
70 + <URL>#<head>
71 ------------
72
73 -`<url>` is required; `#<head>` is optional.
73 +`<URL>` is required; `#<head>` is optional.
74
75 Depending on the operation, git will use one of the following
76 refspecs, if you don't provide one on the command line.