# [PATCH] doc: merge: mention default of defaulttoupstream 3 messages from 2021-06-08 to 2021-06-08. Participants: Felipe Contreras, Junio C Hamano. Thread: https://gitlist.dev/t/55877 ## Felipe Contreras, 2021-06-08 01:58 Subject: [PATCH] doc: merge: mention default of defaulttoupstream Message-ID: <20210608015807.906101-1-felipe.contreras@gmail.com> URL: https://gitlist.dev/e/20210608015807.906101-1-felipe.contreras%40gmail.com ``` Commit a01f7f2ba0 (merge: enable defaulttoupstream by default, 2014-04-20) forgot to mention the new default in the configuration documentation. Signed-off-by: Felipe Contreras --- Documentation/config/merge.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/config/merge.txt b/Documentation/config/merge.txt index cb2ed58907..6b66c83eab 100644 --- a/Documentation/config/merge.txt +++ b/Documentation/config/merge.txt @@ -14,7 +14,7 @@ merge.defaultToUpstream:: branches at the remote named by `branch..remote` are consulted, and then they are mapped via `remote..fetch` to their corresponding remote-tracking branches, and the tips of - these tracking branches are merged. + these tracking branches are merged. Defaults to true. merge.ff:: By default, Git does not create an extra merge commit when merging -- 2.32.0.2.g41be0a4e50 ``` ## Junio C Hamano, 2021-06-08 05:24 Subject: Re: [PATCH] doc: merge: mention default of defaulttoupstream Message-ID: URL: https://gitlist.dev/e/xmqqy2blorn0.fsf%40gitster.g In-Reply-To: <20210608015807.906101-1-felipe.contreras@gmail.com> ``` Felipe Contreras writes: > Commit a01f7f2ba0 (merge: enable defaulttoupstream by default, > 2014-04-20) forgot to mention the new default in the configuration > documentation. > > Signed-off-by: Felipe Contreras > --- > Documentation/config/merge.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/config/merge.txt b/Documentation/config/merge.txt > index cb2ed58907..6b66c83eab 100644 > --- a/Documentation/config/merge.txt > +++ b/Documentation/config/merge.txt > @@ -14,7 +14,7 @@ merge.defaultToUpstream:: > branches at the remote named by `branch..remote` > are consulted, and then they are mapped via `remote..fetch` > to their corresponding remote-tracking branches, and the tips of > - these tracking branches are merged. > + these tracking branches are merged. Defaults to true. That's definititely an improvement. Will queue. By the way, is the convoluted description around remote-tracking branches still understandable to those who often work on a branch forked from another local branch, or would readers be helped if we had a two separate descriptions (one forking from remote and the other forking locally)? This is a side question as the answer does not change the validity of this patch at all. Thanks. ``` ## Felipe Contreras, 2021-06-08 07:29 Subject: Re: [PATCH] doc: merge: mention default of defaulttoupstream Message-ID: <60bf1c49e3f89_1a2cb92082b@natae.notmuch> URL: https://gitlist.dev/e/60bf1c49e3f89_1a2cb92082b%40natae.notmuch In-Reply-To: ``` Junio C Hamano wrote: > Felipe Contreras writes: > > > Commit a01f7f2ba0 (merge: enable defaulttoupstream by default, > > 2014-04-20) forgot to mention the new default in the configuration > > documentation. > > > > Signed-off-by: Felipe Contreras > > --- > > Documentation/config/merge.txt | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/Documentation/config/merge.txt b/Documentation/config/merge.txt > > index cb2ed58907..6b66c83eab 100644 > > --- a/Documentation/config/merge.txt > > +++ b/Documentation/config/merge.txt > > @@ -14,7 +14,7 @@ merge.defaultToUpstream:: > > branches at the remote named by `branch..remote` > > are consulted, and then they are mapped via `remote..fetch` > > to their corresponding remote-tracking branches, and the tips of > > - these tracking branches are merged. > > + these tracking branches are merged. Defaults to true. > > That's definititely an improvement. > > Will queue. > > By the way, is the convoluted description around remote-tracking > branches still understandable to those who often work on a branch > forked from another local branch, or would readers be helped if we > had a two separate descriptions (one forking from remote and the > other forking locally)? I don't think there's any fundamental difference between origin/master, and master. In both cases setting upstream to that simply means "I want `git rebase` to use this by default". There is a separate question of where you should fetch from when upstream is 'master' but that's another topic. What does require explanation is the triangular workflow. Separating descriptions for a triangular worflow, and a two-way workflow might make sense. -- Felipe Contreras ```