Searched refs:blame (Results 1 – 25 of 51) sorted by relevance
123
1 # This is the list of commits that should be ignored by 'git blame'. To4 # git blame --ignore-revs-file .git-blame-ignore-revs6 # To automatically use it when running 'git blame' on this repository, run the9 # git config blame.ignoreRevsFile .git-blame-ignore-revs13 # git config --global blame.ignoreRevsFile .git-blame-ignore-revs17 # their blame view.18 # https://github.blog/changelog/2022-03-24-ignore-commits-in-the-blame-view-beta/
124 git -C "$PW_ROOT" config blame.ignoreRevsFile .git-blame-ignore-revs
90 git -C "$PW_ROOT" config blame.ignoreRevsFile .git-blame-ignore-revs
1 # List of commits to ignore when using `git blame`.3 # git config blame.ignoreRevsFile .git-blame-ignore-revs5 # Per git-blame(1):7 # per line, in git-blame. Whitespace and comments beginning with # are13 # git log -1 --pretty=format:'%n# %s%n%H%n' >> .git-blame-ignore-revs $COMMIT
2 # during git-blame with `--ignore-rev` or `--ignore-revs-file`.4 # $ git config --add 'blame.ignoreRevsFile' '.git-blame-ignore-revs'
13 …blame`. The file `git-blame-ignore-revs` contains the commit hash of when that mass-formatting eve…15 !!! example "Ignoring a commit with `git blame`"17 $ git blame --ignore-revs-file .git-blame-ignore-revs
1 # git hyper-blame master ignore list.4 # hyper-blame (in depot_tools). These revisions are considered "unimportant" in
178 SkString blame("("); in add() local179 blame.append(drp.fBase.fFilename); in add()180 blame.append(", "); in add()181 blame.append(drp.fComparison.fFilename); in add()182 blame.append(")"); in add()183 fResultsOfType[drp.fResult].push_back(std::move(blame)); in add()
1 # .git-blame-ignore-revs
22 through when looking at ``git blame``, you can configure it to ignore25 git config blame.ignoreRevsFile .git-blame-ignore-revs
48 [canonical]: https://github.com/torvalds/linux/blame/master/include/uapi/drm/drm_fourcc.h
27 investigating history and blame, or for exploring release branches or other
84 ; mips/powerpc), maybe before that. Perhaps SelectionDAG is to blame (and
105 need git blame to do this).
49 - Digests are clustered by runs and the most minimal set of blame
74 the patch merged. Also some blame if there are problems.
87 touching. Look at the git blame for the file to see who else has been editing
94 * Use ``svn blame`` and the commit log to find names of people who have
101 * Cc relevant sheriffs or blame suspects, as well as yourself or the current ANGLE Wrangler.
107 owner) reviewer. Running ``git blame`` on the module's source code can
99 targets affected by the patch, so that we don't blame or punish the