git footers extracts information included in commit messages as "footers", which are roughly like HTTP headers except they are at the end\&. For example, a commit might look like:
.sp
.ifn\{\
.RS4
.\}
.nf
This is a fancy commit message\&.
.fi
.ifn\{\
.RE
.\}
.sp
.ifn\{\
.RS4
.\}
.nf
Cr\-Commit\-Position: refs/heads/master@{#292272}
Tech\-Debt\-Introduced: 17 nanoMSOffices
.fi
.ifn\{\
.RE
.\}
.sp
git footers knows how to extract this information\&.
.sp
Footers are order\-independent and can appear more than once\&. Thus they are treated as a multimap\&.
.SH"OPTIONS"
.sp
If no options are given, all footers are printed, with their names case\-normalized\&.
.PP
\-\-key FOOTER
.RS4
Extract all the headers associated with the given key, and print one per line\&. If there are no footers with this key, produces no output and exits successfully\&.
.RE
.PP
\-\-position
.RS4
Extract the Chrome commit position from the footers\&. This first attempts to get the value of the
Cr\-Commit\-Position
footer\&. If that doesn\(cqt exist then it tries a heuristic based on
Git\-Svn\-Id\&. Output is in one of the following forms:
.sp
.ifn\{\
.RS4
.\}
.nf
refs/heads/master@{#292272}
refs/branch\-heads/branchname
.fi
.ifn\{\
.RE
.\}
.RE
.PP
\-\-position\-num
.RS4
Extracts and prints the Chrome commit position number only (292272 in the example above)\&. Exits with an error if one cannot be found\&.
.RE
.PP
\-\-position\-ref
.RS4
Extracts and prints the Chrome commit position ref name only (ref/heads/master
Part of the chromium \fBdepot_tools\fR(7) suite\&. These tools are meant to assist with the development of chromium and related projects\&. Download the tools from \m[blue]\fBhere\fR\m[]\&\s-2\u[1]\d\s+2\&.