48bb914ed6
The point of these sections is generally to:
1. Give credit where it is due.
2. Give the reader an idea of where to ask questions or
file bug reports.
But they don't do a good job of either case. For (1), they
are out of date and incomplete. A much more accurate answer
can be gotten through shortlog or blame. For (2), the
correct contact point is generally git@vger, and even if you
wanted to cc the contact point, the out-of-date and
incomplete fields mean you're likely sending to somebody
useless.
So let's drop the fields entirely from all manpages except
git(1) itself. We already point people to the mailing list
for bug reports there, and we can update the Authors section
to give credit to the major contributors and point to
shortlog and blame for more information.
Each page has a "This is part of git" footer, so people can
follow that to the main git manpage.
29 lines
741 B
Plaintext
29 lines
741 B
Plaintext
git-merge-tree(1)
|
|
=================
|
|
|
|
NAME
|
|
----
|
|
git-merge-tree - Show three-way merge without touching index
|
|
|
|
|
|
SYNOPSIS
|
|
--------
|
|
'git merge-tree' <base-tree> <branch1> <branch2>
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
Reads three treeish, and output trivial merge results and
|
|
conflicting stages to the standard output. This is similar to
|
|
what three-way 'git read-tree -m' does, but instead of storing the
|
|
results in the index, the command outputs the entries to the
|
|
standard output.
|
|
|
|
This is meant to be used by higher level scripts to compute
|
|
merge results outside of the index, and stuff the results back into the
|
|
index. For this reason, the output from the command omits
|
|
entries that match the <branch1> tree.
|
|
|
|
GIT
|
|
---
|
|
Part of the linkgit:git[1] suite
|