Searched refs:blame (Results 1 – 25 of 43) sorted by relevance
12
1 # Since version 2.23 (released in August 2019), git-blame has a feature5 # are looking for in a blame, such as mass reformatting or renaming.6 # You can set this file as a default ignore file for blame by running9 # $ git config blame.ignoreRevsFile .git-blame-ignore-revs
1 # git hyper-blame master ignore list.4 # hyper-blame (in depot_tools). These revisions are considered "unimportant" in
188 SkString* blame = new SkString("("); in add() local189 blame->append(drp->fBase.fFilename); in add()190 blame->append(", "); in add()191 blame->append(drp->fComparison.fFilename); in add()192 blame->append(")"); in add()193 fResultsOfType[drp->fResult].push_back(blame); in add()
193 The costs are that ``git blame`` will become less usable; and that merging the234 Keeping git blame usable237 ``git blame`` (or ``git annotate``) permits quickly identifying the commit that240 blame`` to identify prior, more interesting commits [GreeneGitBlame]_243 **Mitigation**: `git-hyper-blame244 …mmondatastorage.googleapis.com/chrome-infra-docs/flat/depot_tools/docs/html/git-hyper-blame.html>`_246 A ``.git-blame-ignore-revs`` file identifying the variable renaming commits250 whether similar functionality could be added to ``git blame`` itself.269 #. Investigate improving ``git blame``. The extent to which it can be made to
73 * Inspect the repository history (blame, log, bisect) without Internet access.226 commit enables accurate `git blame` when tracking code change history.
19 Ideally these are run for each build in order to make blame easier.
27 investigating history and blame, or for exploring release branches or other
22 investigating history and blame, or for exploring release branches or other
META-INF/MANIFEST.MF META-INF/ECLIPSE_.SF META-INF/ECLIPSE_ ...
... .apache.felix.resolver.ResolverImpl$Blame blame org.osgi.resource.Capability matchingRootCause org. ...
77 ; mips/powerpc), maybe before that. Perhaps SelectionDAG is to blame (and
84 ; mips/powerpc), maybe before that. Perhaps SelectionDAG is to blame (and
49 - Digests are clustered by runs and the most minimal set of blame
46 + Digests are clustered by runs and the most minimal set of blame
82 * Cc relevant sheriffs or blame suspects, as well as yourself or the current ANGLE Wrangler.
87 // we've got a span to blame, let's use it
74 touching. Look at the git blame for the file to see who else has been editing
74 touching. If you have doubts, look at the git blame for the file to see who else
94 * Use ``svn blame`` and the commit log to find names of people who have
138 owner) reviewer. Running ``git blame`` on the module's source code can
128 * Use ``git blame`` and the commit log to find names of people who have
119 base in such a way that tools like "git blame <sourcefile> are still
99 targets affected by the patch, so that we don't blame or punish the
3670 PHEBE If this be so, why blame you me to love you?3672 SILVIUS If this be so, why blame you me to love you?3674 ORLANDO If this be so, why blame you me to love you?3676 ROSALIND Who do you speak to, 'Why blame you me to love you?'