gerrit/.git-blame-ignore-revs
David Pursehouse 17c372a16b Add .git-blame-ignore-revs configuration file for git hyper-blame
The .git-blame-ignore-revs file contains a list of commits to be
ignored by git-hyper-blame [1].

This initial version is based on the one from Chromium [2], and adds
the commit added by change Id5f3c6de9 ("Format all Java files with
google-java-format") to be ignored. The comment at the top is modified
slightly to remove the reference to "depot_tools" and change references
to "CLs" to "commits".

[1] https://commondatastorage.googleapis.com/chrome-infra-docs/flat/depot_tools/docs/html/git-hyper-blame.html
[2] https://chromium.googlesource.com/chromium/src.git/+/master/.git-blame-ignore-revs

Change-Id: I477f19580d782514f0811a05a0bdc6acae7fddb0
2017-02-08 08:22:23 +09:00

23 lines
1.2 KiB
Plaintext

# git hyper-blame master ignore list.
#
# This file contains a list of git hashes of revisions to be ignored by git
# hyper-blame. These revisions are considered "unimportant" in that they are
# unlikely to be what you are interested in when blaming.
#
# Instructions:
# - Only large (generally automated) reformatting or renaming commits should be
# added to this list. Do not put things here just because you feel they are
# trivial or unimportant. If in doubt, do not put it on this list.
# - Precede each revision with a comment containing the first line of its log.
# For bulk work over many commits, place all commits in a block with a single
# comment at the top describing the work done in those commits.
# - Only put full 40-character hashes on this list (not short hashes or any
# other revision reference).
# - Append to the bottom of the file (revisions should be in chronological order
# from oldest to newest).
# - Because you must use a hash, you need to append to this list in a follow-up
# commit to the actual reformatting commit that you are trying to ignore.
# Format all Java files with google-java-format
292fa154c18b5a203c1aa211dce4efd54e6e8e0a