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

[James Y Knight via llvm-dev]

As a very frequent explorer of history, I really don't think this is
as big an issue as it may seem. Even absent refactorings, you often
run into the "wrong" commit when looking at blame (e.g., someone just
added a comma rather than actually changing the code you care about),
and have to look past that, to another previous commit.

Any interactive blame tool ought to have an easy way to do this. For
example, in emacs's annotation mode (which is what I use), you just
press 'a' with the cursor on the line in question to re-annotate at
the commit previous to that.

On Tue, Jul 23, 2019 at 11:25 AM Peter Waller via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
>
> 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