The documentation for branch.*.merge is very dense, so add a simple explanation on top of it. And branch.*.remote also afects 'git push'. Text taken from 'push.default'. Signed-off-by: Santi Béjar <santi@xxxxxxxxxxx> --- Documentation/config.txt | 8 ++++++-- 1 files changed, 6 insertions(+), 2 deletions(-) diff --git a/Documentation/config.txt b/Documentation/config.txt index 089569a..56f0cd7 100644 --- a/Documentation/config.txt +++ b/Documentation/config.txt @@ -473,10 +473,14 @@ branch.autosetuprebase:: This option defaults to never. branch.<name>.remote:: - When in branch <name>, it tells 'git-fetch' which remote to fetch. - If this option is not given, 'git-fetch' defaults to remote "origin". + When in branch <name>, it tells 'git-fetch' and 'git-push' which + remote to fetch/push, and defaults to `origin` if no remote is + configured. `origin` is also used if you are not on any branch. branch.<name>.merge:: + It defines, together with branch.<name>.remote, the tracking branch + for the current branch. It tells 'git-fetch'/'git-pull' which + branch to merge. When in branch <name>, it tells 'git-fetch' the default refspec to be marked for merging in FETCH_HEAD. The value is handled like the remote part of a refspec, and must match a -- 1.6.1.258.g7ff14 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
