Linus Torvalds writes: (Summary)
So generally, if you do the test-merge anyway (which I appreciate), I
generally prefer the expected results instead of the raw `git
request-pull` output.
request-pull` output.
But it's also definitely not a hard requirement.
But it's also definitely not a hard requirement.
Basically, the rough guidance is that "git request-pull is sufficient". And if you are not a git power-user (ie you don't use lots of branches, and there aren't any shared topic branches with other trees), git request-pull will simply always be the right thing anyway. For maintainers that _are_ doing fancier things with git, and are sharing branches and doing their own complex git history, "git request-pull" is the simple interface - and is generally _too_ simple.
request-pull` output.
But it's also definitely not a hard requirement.
But it's also definitely not a hard requirement.
Basically, the rough guidance is that "git request-pull is sufficient". And if you are not a git power-user (ie you don't use lots of branches, and there aren't any shared topic branches with other trees), git request-pull will simply always be the right thing anyway. For maintainers that _are_ doing fancier things with git, and are sharing branches and doing their own complex git history, "git request-pull" is the simple interface - and is generally _too_ simple.