On Mon, 23 Jan 2023, Ed Maste wrote:

The branch main has been updated by emaste:

URL: 
https://cgit.FreeBSD.org/src/commit/?id=247e03ed8b8341cf25dc3d9ecb846612d984f424

commit 247e03ed8b8341cf25dc3d9ecb846612d984f424
Author:     Ed Maste <ema...@freebsd.org>
AuthorDate: 2023-01-23 20:27:25 +0000
Commit:     Ed Maste <ema...@freebsd.org>
CommitDate: 2023-01-23 20:27:25 +0000

   Add git-blame ignore file

   .git-blame-ignore-revs lists commit hashes that should be skipped by
   `git blame` e.g. non-functional whitespace or style cleanup.

   The file is populated with a few sample entries.

How is this file to be used?

1. Do a non-functional commit?
2. And then do another commit to add the hash?

And do we really need the comments?  I am wondering if a flag in the
original commit message could automatically populate the file on
push/commit or something?  (I don't know the git internals...)


   Reviewed by:    brooks, imp
   Sponsored by:   The FreeBSD Foundation
   Differential Revision:  https://reviews.freebsd.org/D36525

   fixup ignore revs
---
.git-blame-ignore-revs | 16 ++++++++++++++++
1 file changed, 16 insertions(+)

diff --git a/.git-blame-ignore-revs b/.git-blame-ignore-revs
new file mode 100644
index 000000000000..2a4ab51f89c1
--- /dev/null
+++ b/.git-blame-ignore-revs
@@ -0,0 +1,16 @@
+# List of hashes of non-functional changes to be ignored by git-blame.
+# This includes whitespace, style(9), comment typos, etc.  Changes that affect
+# built objects must not be included.
+#
+# Use `git blame --ignore-revs-file .git-blame-ignore-revs` or configure via
+# `git config --global blame.ignoreRevsFile .git-blame-ignore-revs`.  GitHub's
+# blame view also uses this by default.
+#
+# For consistency this file is sorted by hash.
+
+# regen syscall files after d51198d63b63
+2c9764f36b6f20e9a6c71ce64a21988a394050b6
+# Remove whitespace at EOL.
+7ebcc426efefea9cd16ac6f565e72030c608f7a4
+# elfctl whitespace
+828e50092ac84f50247fb3f400027fc7510d8141


--
Bjoern A. Zeeb                                                     r15:7

Reply via email to