[llvm-dev] RFC: changing variable naming rules in LLVM codebase & git-blame

[Chikin, Artem via llvm-dev]

This will be a git feature in git 2.23 (in Q3 2019).
It will allow git blame to ignore revisions with --ignore-rev, which the user can even specify in their git config.

Relevant git blame documentation change:
https://github.com/git/git/blob/ae3f36dea16e51041c56ba9ed6b38380c8421816/Documentation/blame-options.txt#L113-L125

Relevant git config documentation change:
https://github.com/git/git/blob/ae3f36dea16e51041c56ba9ed6b38380c8421816/Documentation/config/blame.txt#L23-L28

-----Original Message-----
From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of Peter Waller via llvm-dev
Sent: Tuesday, July 23, 2019 11:25
To: llvm-dev at lists.llvm.org
Cc: nd <nd at arm.com>
Subject: Re: [llvm-dev] RFC: changing variable naming rules in LLVM codebase & git-blame

On 7/22/19 6:34 PM, JF Bastien via llvm-dev wrote:
> * How do we expect to maintain git blame history, if at all?

Hmm. I was hoping git-blame would have a feature which might allow ignoring commits, but seemingly not. You can ignore whitespace changes with -w, but of course that doesn't help for variable names.

It seems the next best thing is to blame starting at a revision. At least if there is "one big change", there is only one revision to consider. With many smaller changes that would be harder.

_______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev