[Master] Ignoring mass reformatting commits with git blame

[mozga-intel]

Description

Ignoring bulk change commits with git blame ~ Using --ignore-rev, one can specify a commit to be ignored by git blame.

We can call git blame with the --ignore-revs-file option to ignore all these commits at once:

git config blame.ignoreRevsFile .git-blame-ignore-revs

Before:

e359bcd65e (mozga        2021-09-13 15:28:22 +0200  38)     .set_body([](runtime::MXNetArgs args, runtime::MXNetRetValue* ret) {
e359bcd65e (mozga        2021-09-13 15:28:22 +0200  39)       using namespace runtime;
e359bcd65e (mozga        2021-09-13 15:28:22 +0200  40)       if (args[0].type_code() == kDLInt) {
e359bcd65e (mozga        2021-09-13 15:28:22 +0200  41)         *ret = Integer(args[0].operator int64_t());
e359bcd65e (mozga        2021-09-13 15:28:22 +0200  42)       } else {
e359bcd65e (mozga        2021-09-13 15:28:22 +0200  43)         LOG(FATAL) << "only accept int";
e359bcd65e (mozga        2021-09-13 15:28:22 +0200  44)       }
e359bcd65e (mozga        2021-09-13 15:28:22 +0200  45)     });

After:

3f0b049a30 (Haozheng Fan 2020-02-25 04:47:23 +0800  38)     .set_body([](runtime::MXNetArgs args, runtime::MXNetRetValue* ret) {
3f0b049a30 (Haozheng Fan 2020-02-25 04:47:23 +0800  39)       using namespace runtime;
3f0b049a30 (Haozheng Fan 2020-02-25 04:47:23 +0800  40)       if (args[0].type_code() == kDLInt) {
3f0b049a30 (Haozheng Fan 2020-02-25 04:47:23 +0800  41)         *ret = Integer(args[0].operator int64_t());
3f0b049a30 (Haozheng Fan 2020-02-25 04:47:23 +0800  42)       } else {
3f0b049a30 (Haozheng Fan 2020-02-25 04:47:23 +0800  43)         LOG(FATAL) << "only accept int";
3f0b049a30 (Haozheng Fan 2020-02-25 04:47:23 +0800  44)       }
3f0b049a30 (Haozheng Fan 2020-02-25 04:47:23 +0800  45)     });

Checklist

Essentials

• PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
• Changes are complete (i.e. I finished coding on this PR)
• All changes have test coverage
• Code is well-documented

Changes

• Feature1, tests, (and when applicable, API doc)
• Feature2, tests, (and when applicable, API doc)

Comments

• If this change is a backward incompatible change, why must this change be made.
• Interesting edge cases to note here

[mxnet-bot]

Hey @mozga-intel , Thanks for submitting the PR
All tests are already queued to run once. If tests fail, you can trigger one or more tests again with the following commands:

• To trigger all jobs: @mxnet-bot run ci [all]
• To trigger specific jobs: @mxnet-bot run ci [job1, job2]

---

CI supported jobs: [centos-cpu, miscellaneous, unix-gpu, edge, windows-gpu, centos-gpu, clang, sanity, windows-cpu, unix-cpu, website]

---

Note:
Only following 3 categories can trigger CI :PR Author, MXNet Committer, Jenkins Admin.
All CI tests must pass before the PR can be merged.

[mozga-intel]

@mxnet-bot run ci [windows-gpu, windows-cpu, centos-gpu]

[mxnet-bot]

Jenkins CI successfully triggered : [windows-gpu, centos-gpu, windows-cpu]

[mozga-intel]

@mxnet-bot run ci [centos-gpu]

[mxnet-bot]

Jenkins CI successfully triggered : [centos-gpu]

[mxnet-bot]

Jenkins CI successfully triggered : [centos-gpu]

[mozga-intel]

@mxnet-bot run ci [centos-gpu, centos-cpu]

[mozga-intel]

@mxnet-bot run ci [centos-gpu, centos-cpu, windows-gpu]

[mxnet-bot]

Jenkins CI successfully triggered : [centos-cpu, windows-gpu, centos-gpu]

[mozga-intel]

@mxnet-bot run ci [all]

[mxnet-bot]

Jenkins CI successfully triggered : [clang, miscellaneous, windows-cpu, website, sanity, unix-cpu, centos-gpu, centos-cpu, windows-gpu, unix-gpu, edge]