@matheusbsbs / matheus-bagliano / commits / 9d13bda3ff
Fork 0

user-manual: repo-config -> config

Looks like we're going to allow git-config as the preferred alias to git-repo-config, so let's document that instead. Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>

J. Bruce Fields committed Jan 28, 2007 at 23:50 UTC 9d13bda3fffc948c0b2576f08a33ac7f547fe9b3
1 file changed +9 -9
Documentation/user-manual.txt
+9 -9
@@ -1450,7 +1450,7 @@ $ git pull
1450 -------------------------------------------------
1451
1452 See the descriptions of the branch.<name>.remote and
1453 -branch.<name>.merge options in gitlink:git-repo-config[1] to learn
1453 +branch.<name>.merge options in gitlink:git-config[1] to learn
1454 how to control these defaults depending on the current branch.
1455
1456 In addition to saving you keystrokes, "git pull" also helps you by
@@ -1685,7 +1685,7 @@ $ git push public-repo master
1685 -------------------------------------------------
1686
1687 See the explanations of the remote.<name>.url, branch.<name>.remote,
1688 -and remote.<name>.push options in gitlink:git-repo-config[1] for
1688 +and remote.<name>.push options in gitlink:git-config[1] for
1689 details.
1690
1691 Setting up a shared repository
@@ -1999,10 +1999,10 @@ Configuring remote branches
1999 We saw above that "origin" is just a shortcut to refer to the
2000 repository which you originally cloned from. This information is
2001 stored in git configuration variables, which you can see using
2002 -gitlink:git-repo-config[1]:
2002 +gitlink:git-config[1]:
2003
2004 -------------------------------------------------
2005 -$ git-repo-config -l
2005 +$ git config -l
2006 core.repositoryformatversion=0
2007 core.filemode=true
2008 core.logallrefupdates=true
@@ -2017,7 +2017,7 @@ create similar configuration options to save typing; for example,
2017 after
2018
2019 -------------------------------------------------
2020 -$ git repo-config remote.example.url git://example.com/proj.git
2020 +$ git config remote.example.url git://example.com/proj.git
2021 -------------------------------------------------
2022
2023 then the following two commands will do the same thing:
@@ -2030,7 +2030,7 @@ $ git fetch example master:refs/remotes/example/master
2030 Even better, if you add one more option:
2031
2032 -------------------------------------------------
2033 -$ git repo-config remote.example.fetch master:refs/remotes/example/master
2033 +$ git config remote.example.fetch master:refs/remotes/example/master
2034 -------------------------------------------------
2035
2036 then the following commands will all do the same thing:
@@ -2045,7 +2045,7 @@ $ git fetch example
2045 You can also add a "+" to force the update each time:
2046
2047 -------------------------------------------------
2048 -$ git repo-config remote.example.fetch +master:ref/remotes/example/master
2048 +$ git config remote.example.fetch +master:ref/remotes/example/master
2049 -------------------------------------------------
2050
2051 Don't do this unless you're sure you won't mind "git fetch" possibly
@@ -2053,9 +2053,9 @@ throwing away commits on mybranch.
2053
2054 Also note that all of the above configuration can be performed by
2055 directly editing the file .git/config instead of using
2056 -gitlink:git-repo-config[1].
2056 +gitlink:git-config[1].
2057
2058 -See gitlink:git-repo-config[1] for more details on the configuration
2058 +See gitlink:git-config[1] for more details on the configuration
2059 options mentioned above.
2060
2061