Re: git: 247e03ed8b83 - main - Add git-blame ignore file
- In reply to: Ed Maste : "Re: git: 247e03ed8b83 - main - Add git-blame ignore file"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 27 Jan 2023 20:03:40 UTC
On Fri, Jan 27, 2023, 12:59 PM Ed Maste <emaste@freebsd.org> wrote: > On Fri, 27 Jan 2023 at 10:24, Bjoern A. Zeeb <bz@freebsd.org> wrote: > > > > 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 <emaste@FreeBSD.org> > > > AuthorDate: 2023-01-23 20:27:25 +0000 > > > Commit: Ed Maste <emaste@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? > > Yes, although there's no need to list every non-functional change > here. It's useful mainly for changes that would otherwise obscure the > history/blame - for example, re-indenting libexec/rtld-elf/rtld.c to > use standard indentation would be a good use. > > We could omit the comments, but I don't think it's worth the effort to > try to automate this. > Yea, we need a hash to put in the file which suggests that at most we could do automatically is add a new commit at the end of the push... and that's going to cause extra friction if we do it too much. And if we do it rarely, there's little benefit to automation. And reformatting is very rare.... Warner >