1GIT-CONTACTS(1)                   Git Manual                   GIT-CONTACTS(1)
2
3
4

NAME

6       git-contacts - List people who might be interested in a set of changes
7

SYNOPSIS

9       git contacts (<patch>|<range>|<rev>)...
10
11

DESCRIPTION

13       Given a set of changes, specified as patch files or revisions,
14       determine people who might be interested in those changes. This is done
15       by consulting the history of each patch or revision hunk to find people
16       mentioned by commits which touched the lines of files under
17       consideration.
18
19       Input consists of one or more patch files or revision arguments. A
20       revision argument can be a range or a single <rev> which is interpreted
21       as <rev>..HEAD, thus the same revision arguments are accepted as for
22       git-format-patch(1). Patch files and revision arguments can be combined
23       in the same invocation.
24
25       This command can be useful for determining the list of people with whom
26       to discuss proposed changes, or for finding the list of recipients to
27       Cc: when submitting a patch series via git send-email. For the latter
28       case, git contacts can be used as the argument to git send-email's
29       --cc-cmd option.
30

DISCUSSION

32       git blame is invoked for each hunk in a patch file or revision. For
33       each commit mentioned by git blame, the commit message is consulted for
34       people who authored, reviewed, signed, acknowledged, or were Cc:'d.
35       Once the list of participants is known, each person’s relevance is
36       computed by considering how many commits mentioned that person compared
37       with the total number of commits under consideration. The final output
38       consists only of participants who exceed a minimum threshold of
39       participation.
40

OUTPUT

42       For each person of interest, a single line is output, terminated by a
43       newline. If the person’s name is known, “Name <user@host>” is printed;
44       otherwise only “<user@host>” is printed.
45

EXAMPLES

47       ·   Consult patch files:
48
49               $ git contacts feature/*.patch
50
51
52       ·   Revision range:
53
54               $ git contacts R1..R2
55
56
57       ·   From a single revision to HEAD:
58
59               $ git contacts origin
60
61
62       ·   Helper for git send-email:
63
64               $ git send-email --cc-cmd='git contacts' feature/*.patch
65
66

LIMITATIONS

68       Several conditions controlling a person’s significance are currently
69       hard-coded, such as minimum participation level (10%), blame
70       date-limiting (5 years), and -C level for detecting moved and copied
71       lines (a single -C). In the future, these conditions may become
72       configurable.
73

GIT

75       Part of the git(1) suite
76
77
78
79Git 2.21.0                        02/24/2019                   GIT-CONTACTS(1)
Impressum