Thread (1 message) 1 message, 1 author, 2016-06-15
  • (off-list ancestor, not in this archive)
  • Re: merge summaries · Junio C Hamano <hidden> · 2016-06-15

Re: merge summaries

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:11

Steffen Prohaska [off-list ref] writes:
But this is true not only for the upstream master but for every branch.
The first-parent-path of any commit documents (at least in summaries)
which features were introduced to the branch at which place. If a
topic pulls from upstream, features already available in the upstream
are introduced to the topic at this time. Why not summarize this?
Strictly speaking, it is not even correct with the upstream
master.  I believe even my own 'maint' has fast forward merge
that I pulled from other people, and that part of the history if
you follow first-parent, you would not be following the "project's"
history (if there is such a thing, and if you are equating it
with "JC's view of the history").
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help