git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 02/10] Replace "remote tracking" with "remote-tracking"

From
Matthieu Moy <matthieu.moy@imag.fr>
Date
Oct 28, 2010, 18:21 UTC
Message-ID
<1288290117-6734-3-git-send-email-Matthieu.Moy@imag.fr>
In-Reply-To
<1287851481-27952-1-git-send-email-Matthieu.Moy@imag.fr>

"remote-tracking" branch makes it explicit that the branch is "tracking a remote", as opposed to "remote, and tracking something".

See discussion in e.g. http://mid.gmane.org/8835ADF9-45E5-4A26-9F7F-A72ECC065BB2@gmail.com for more details.

This patch is a straightforward application of
  perl -pi -e 's/remote tracking branch/remote-tracking branch/'
except in the RelNotes directory.
Signed-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>
---
 Documentation/config.txt           |    2 +-
 Documentation/fetch-options.txt    |    2 +-
 Documentation/git-log.txt          |    2 +-
 Documentation/git-pull.txt         |    2 +-
 Documentation/git-remote.txt       |    4 ++--
 Documentation/gittutorial.txt      |    2 +-
 Documentation/rev-list-options.txt |    2 +-
 Documentation/user-manual.txt      |    2 +-
 builtin/checkout.c                 |    2 +-
 t/t5513-fetch-track.sh             |    2 +-
 10 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index 538ebb5..e625d6a 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -708,7 +708,7 @@ color.diff.<slot>::
 color.decorate.<slot>::
 	Use customized color for 'git log --decorate' output.  `<slot>` is one
 	of `branch`, `remoteBranch`, `tag`, `stash` or `HEAD` for local
-	branches, remote tracking branches, tags, stash and HEAD, respectively.
+	branches, remote-tracking branches, tags, stash and HEAD, respectively.
 
 color.grep::
 	When set to `always`, always highlight matches.  When `false` (or
diff --git a/Documentation/fetch-options.txt b/Documentation/fetch-options.txt
index 470ac31..a435c23 100644
--- a/Documentation/fetch-options.txt
+++ b/Documentation/fetch-options.txt
@@ -36,7 +36,7 @@ ifndef::git-pull[]
 
 -p::
 --prune::
-	After fetching, remove any remote tracking branches which
+	After fetching, remove any remote-tracking branches which
 	no longer exist	on the remote.
 endif::git-pull[]
 
diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
index 6d40f00..ff41784 100644
--- a/Documentation/git-log.txt
+++ b/Documentation/git-log.txt
@@ -116,7 +116,7 @@ git log --follow builtin-rev-list.c::
 git log --branches --not --remotes=origin::
 
 	Shows all commits that are in any of local branches but not in
-	any of remote tracking branches for 'origin' (what you have that
+	any of remote-tracking branches for 'origin' (what you have that
 	origin doesn't).
 
 git log master --not --remotes=*/master::
diff --git a/Documentation/git-pull.txt b/Documentation/git-pull.txt
index c50f7dc..33e8438 100644
--- a/Documentation/git-pull.txt
+++ b/Documentation/git-pull.txt
@@ -26,7 +26,7 @@ With `--rebase`, it runs 'git rebase' instead of 'git merge'.
 <repository> should be the name of a remote repository as
 passed to linkgit:git-fetch[1].  <refspec> can name an
 arbitrary remote ref (for example, the name of a tag) or even
-a collection of refs with corresponding remote tracking branches
+a collection of refs with corresponding remote-tracking branches
 (e.g., refs/heads/*:refs/remotes/origin/*), but usually it is
 the name of a branch in the remote repository.
 
diff --git a/Documentation/git-remote.txt b/Documentation/git-remote.txt
index 0d28feb..5e4989d 100644
--- a/Documentation/git-remote.txt
+++ b/Documentation/git-remote.txt
@@ -75,7 +75,7 @@ was passed.
 
 'rename'::
 
-Rename the remote named <old> to <new>. All remote tracking branches and
+Rename the remote named <old> to <new>. All remote-tracking branches and
 configuration settings for the remote are updated.
 +
 In case <old> and <new> are the same, and <old> is a file under
@@ -84,7 +84,7 @@ the configuration file format.
 
 'rm'::
 
-Remove the remote named <name>. All remote tracking branches and
+Remove the remote named <name>. All remote-tracking branches and
 configuration settings for the remote are removed.
 
 'set-head'::
diff --git a/Documentation/gittutorial.txt b/Documentation/gittutorial.txt
index 1c16066..f1f4086 100644
--- a/Documentation/gittutorial.txt
+++ b/Documentation/gittutorial.txt
@@ -385,7 +385,7 @@ alice$ git fetch bob
 
 Unlike the longhand form, when Alice fetches from Bob using a
 remote repository shorthand set up with 'git remote', what was
-fetched is stored in a remote tracking branch, in this case
+fetched is stored in a remote-tracking branch, in this case
 `bob/master`.  So after this:
 
 -------------------------------------
diff --git a/Documentation/rev-list-options.txt b/Documentation/rev-list-options.txt
index 7a42567..7a1b164 100644
--- a/Documentation/rev-list-options.txt
+++ b/Documentation/rev-list-options.txt
@@ -264,7 +264,7 @@ endif::git-rev-list[]
 
 	Pretend as if all the refs in `refs/remotes` are listed
 	on the command line as '<commit>'. If '<pattern>' is given, limit
-	remote tracking branches to ones matching given shell glob.
+	remote-tracking branches to ones matching given shell glob.
 	If pattern lacks '?', '*', or '[', '/*' at the end is implied.
 
 --glob=<glob-pattern>::
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index fc56da6..d5505e8 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -1700,7 +1700,7 @@ may wish to check the original repository for updates and merge them
 into your own work.
 
 We have already seen <<Updating-a-repository-With-git-fetch,how to
-keep remote tracking branches up to date>> with linkgit:git-fetch[1],
+keep remote-tracking branches up to date>> with linkgit:git-fetch[1],
 and how to merge two branches.  So you can merge in changes from the
 original repository's master branch with:
 
diff --git a/builtin/checkout.c b/builtin/checkout.c
index 9240faf..9a934af 100644
--- a/builtin/checkout.c
+++ b/builtin/checkout.c
@@ -786,7 +786,7 @@ int cmd_checkout(int argc, const char **argv, const char *prefix)
 	 *   With no paths, if <something> is _not_ a commit, no -t nor -b
 	 *   was given, and there is a tracking branch whose name is
 	 *   <something> in one and only one remote, then this is a short-hand
-	 *   to fork local <something> from that remote tracking branch.
+	 *   to fork local <something> from that remote-tracking branch.
 	 *
 	 *   Otherwise <something> shall not be ambiguous.
 	 *   - If it's *only* a reference, treat it like case (1).
diff --git a/t/t5513-fetch-track.sh b/t/t5513-fetch-track.sh
index 9e74862..65d1e05 100755
--- a/t/t5513-fetch-track.sh
+++ b/t/t5513-fetch-track.sh
@@ -1,6 +1,6 @@
 #!/bin/sh
 
-test_description='fetch follows remote tracking branches correctly'
+test_description='fetch follows remote-tracking branches correctly'
 
 . ./test-lib.sh
 
-- 
1.7.3.2.183.g2e7b0
Previous: Matthieu MoyNext: Jonathan Nieder
Message 65 of 101 in “More consistant terminology ("remote-tracking branch", "not updated")”
  1. 00/11 More consistant terminology ("remote-tracking branch", "not updated")Matthieu Moy, Oct 23, 2010
  2. 01/10 Better "Changed but not updated" message in git-statusMatthieu Moy, Oct 23, 2010
  3. Jonathan NiederOct 23, 2010
  4. Matthieu MoyOct 23, 2010
  5. Jakub NarebskiOct 23, 2010
  6. 02/10 Remplace "remote tracking" with "remote-tracking"Matthieu Moy, Oct 23, 2010
  7. Jonathan NiederOct 23, 2010
  8. Jonathan NiederOct 23, 2010
  9. Matthieu MoyOct 23, 2010
  10. 03/10 Change remote tracking to remote-tracking in non-trivial placesMatthieu Moy, Oct 23, 2010
  11. Jonathan NiederOct 23, 2010
  12. Matthieu MoyOct 23, 2010
  13. 04/10 Change "tracking branch" to "remote-tracking branch"Matthieu Moy, Oct 23, 2010
  14. Jonathan NiederOct 23, 2010
  15. Matthieu MoyOct 28, 2010
  16. 05/10 Change "tracking branch" to "remote-tracking branch" in C codeMatthieu Moy, Oct 23, 2010
  17. Jonathan NiederOct 23, 2010
  18. Matthieu MoyOct 26, 2010
  19. 06/10 Change incorrect uses of "remote branch" meaning "remote-tracking"Matthieu Moy, Oct 23, 2010
  20. 07/10 Change incorrect "remote branch" to "remote tracking branch" in C codeMatthieu Moy, Oct 23, 2010
  21. Jonathan NiederOct 23, 2010
  22. Matthieu MoyOct 23, 2010
  23. 08/10 Use 'remote-tracking branch' in generated merge messagesMatthieu Moy, Oct 23, 2010
  24. Jonathan NiederOct 23, 2010
  25. Matthieu MoyOct 23, 2010
  26. 09/10 user-manual.txt: explain better the remote(-tracking) branch termsMatthieu Moy, Oct 23, 2010
  27. Jonathan NiederOct 23, 2010
  28. Matthieu MoyOct 23, 2010
  29. Thore HusfeldtOct 24, 2010
  30. Jonathan NiederOct 24, 2010
  31. Jakub NarebskiOct 24, 2010
  32. Matthieu MoyOct 26, 2010
  33. Miles BaderOct 26, 2010
  34. 10/10 git-branch.txt: mention --set-upstream as a way to change upstream configurationMatthieu Moy, Oct 23, 2010
  35. Jakub NarebskiOct 23, 2010
  36. Jonathan NiederOct 23, 2010
  37. Matthieu MoyOct 25, 2010
  38. 00/10 More consistant terminology ("remote-tracking branch", "not updated")Matthieu Moy, Oct 25, 2010
  39. 01/10 Better "Changed but not updated" message in git-statusMatthieu Moy, Oct 25, 2010
  40. 02/10 Replace "remote tracking" with "remote-tracking"Matthieu Moy, Oct 25, 2010
  41. 03/10 Change remote tracking to remote-tracking in non-trivial placesMatthieu Moy, Oct 25, 2010
  42. 04/10 Change "tracking branch" to "remote-tracking branch"Matthieu Moy, Oct 25, 2010
  43. 05/10 Change "tracking branch" to "remote-tracking branch" in C codeMatthieu Moy, Oct 25, 2010
  44. 06/10 Change incorrect uses of "remote branch" meaning "remote-tracking"Matthieu Moy, Oct 25, 2010
  45. 07/10 Change incorrect "remote branch" to "remote tracking branch" in C codeMatthieu Moy, Oct 25, 2010
  46. 08/10 Use 'remote-tracking branch' in generated merge messagesMatthieu Moy, Oct 25, 2010
  47. 09/10 user-manual.txt: explain better the remote(-tracking) branch termsMatthieu Moy, Oct 25, 2010
  48. Jay SoffianOct 26, 2010
  49. Matthieu MoyOct 26, 2010
  50. Jay SoffianOct 26, 2010
  51. Matthieu MoyOct 27, 2010
  52. user-manual.txt: explain better the remote(-tracking) branch termsMatthieu Moy, Oct 27, 2010
  53. 10/10 git-branch.txt: mention --set-upstream as a way to change upstream configurationMatthieu Moy, Oct 25, 2010
  54. Drew NorthupOct 25, 2010
  55. 00/10 More consistant terminology ("remote-tracking branch", "not updated")Matthieu Moy, Oct 28, 2010
  56. 01/10 Better "Changed but not updated" message in git-statusMatthieu Moy, Oct 28, 2010
  57. Jonathan NiederOct 28, 2010
  58. Junio C HamanoOct 28, 2010
  59. Jonathan NiederOct 28, 2010
  60. Matthieu MoyOct 28, 2010
  61. Junio C HamanoOct 28, 2010
  62. Matthieu MoyOct 28, 2010
  63. Drew NorthupOct 29, 2010
  64. Matthieu MoyOct 30, 2010
  65. 02/10 Replace "remote tracking" with "remote-tracking"Matthieu Moy, Oct 28, 2010
  66. Jonathan NiederOct 28, 2010
  67. 03/10 Change remote tracking to remote-tracking in non-trivial placesMatthieu Moy, Oct 28, 2010
  68. Jonathan NiederOct 28, 2010
  69. Matthieu MoyOct 28, 2010
  70. Jonathan NiederOct 28, 2010
  71. Matthieu MoyOct 28, 2010
  72. Drew NorthupOct 29, 2010
  73. 04/10 Change "tracking branch" to "remote-tracking branch"Matthieu Moy, Oct 28, 2010
  74. Jonathan NiederOct 28, 2010
  75. 05/10 Change incorrect uses of "remote branch" meaning "remote-tracking"Matthieu Moy, Oct 28, 2010
  76. 06/10 Change incorrect "remote branch" to "remote tracking branch" in C codeMatthieu Moy, Oct 28, 2010
  77. Jonathan NiederOct 28, 2010
  78. Matthieu MoyOct 28, 2010
  79. Jonathan NiederOct 28, 2010
  80. 07/10 Use 'remote-tracking branch' in generated merge messagesMatthieu Moy, Oct 28, 2010
  81. 08/10 user-manual.txt: explain better the remote(-tracking) branch termsMatthieu Moy, Oct 28, 2010
  82. Jonathan NiederOct 28, 2010
  83. Matthieu MoyOct 28, 2010
  84. 09/10 user-manual: remote-tracking can be checked out, with detached HEADMatthieu Moy, Oct 28, 2010
  85. 10/10 git-branch.txt: mention --set-upstream as a way to change upstream configurationMatthieu Moy, Oct 28, 2010
  86. Jonathan NiederOct 28, 2010
  87. 00/11 More consistant terminologyMatthieu Moy, Oct 30, 2010
  88. Jonathan NiederOct 30, 2010
  89. 01/11 Better "Changed but not updated" message in git-statusMatthieu Moy, Oct 30, 2010
  90. 02/11 Replace "remote tracking" with "remote-tracking"Matthieu Moy, Oct 30, 2010
  91. 03/11 Change remote tracking to remote-tracking in non-trivial placesMatthieu Moy, Oct 30, 2010
  92. 04/11 everyday.txt: change "tracking branch" to "remote-tracking branch"Matthieu Moy, Oct 30, 2010
  93. 05/11 Change "tracking branch" to "remote-tracking branch"Matthieu Moy, Oct 30, 2010
  94. 06/11 Change incorrect uses of "remote branch" meaning "remote-tracking"Matthieu Moy, Oct 30, 2010
  95. 07/11 Change incorrect "remote branch" to "remote tracking branch" in C codeMatthieu Moy, Oct 30, 2010
  96. 08/11 Use 'remote-tracking branch' in generated merge messagesMatthieu Moy, Oct 30, 2010
  97. 09/11 user-manual.txt: explain better the remote(-tracking) branch termsMatthieu Moy, Oct 30, 2010
  98. Jonathan NiederOct 30, 2010
  99. Matthieu MoyOct 31, 2010
  100. 10/11 user-manual: remote-tracking can be checked out, with detached HEADMatthieu Moy, Oct 30, 2010
  101. 11/11 git-branch.txt: mention --set-upstream as a way to change upstream configurationMatthieu Moy, Oct 30, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.