[PATCH V2 2/3] config doc: update dot-repository notes
- From
Philip Oakley <philipoakley@iee.org>
- Date
- Sep 13, 2013, 21:23 UTC
- Message-ID
- <1379107397-964-3-git-send-email-philipoakley@iee.org>
- In-Reply-To
- <1379107397-964-1-git-send-email-philipoakley@iee.org>
branch.<name>.remote can be set to '.' (period) as the repository path (URL) as part of the remote name dwimmery. Tell the reader.
Such relative paths are not 'special'. Correct the branch.<name>.merge note.
Signed-off-by: Philip Oakley <philipoakley@iee.org> --- Documentation/config.txt | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt index 599ca52..da63043 100644 --- a/Documentation/config.txt +++ b/Documentation/config.txt @@ -718,6 +718,8 @@ branch.<name>.remote:: overridden by `branch.<name>.pushremote`. If no remote is configured, or if you are not on any branch, it defaults to `origin` for fetching and `remote.pushdefault` for pushing. + Additionally, `.` (a period) is the current local repository + (a dot-repository), see `branch.<name>.merge`'s final note below. branch.<name>.pushremote:: When on branch <name>, it overrides `branch.<name>.remote` for @@ -743,8 +745,8 @@ branch.<name>.merge:: Specify multiple values to get an octopus merge. If you wish to setup 'git pull' so that it merges into <name> from another branch in the local repository, you can point - branch.<name>.merge to the desired branch, and use the special setting - `.` (a period) for branch.<name>.remote. + branch.<name>.merge to the desired branch, and use the relative path + setting `.` (a period) for branch.<name>.remote. branch.<name>.mergeoptions:: Sets default options for merging into branch <name>. The syntax and
-- 1.8.1.msysgit.1