Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 02 Jun 2021 16:16:54 -0500
From:   Felipe Contreras <felipe.contreras@gmail.com>
To:     Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
        git@vger.kernel.org
Cc:     Peter Zijlstra <peterz@infradead.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        linux-kernel <linux-kernel@vger.kernel.org>,
        Jiri Kosina <trivial@kernel.org>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Message-ID: <60b7f54697fda_16925f2083d@natae.notmuch>
In-Reply-To: <30399052.5964.1622647235870.JavaMail.zimbra@efficios.com>
References: <30399052.5964.1622647235870.JavaMail.zimbra@efficios.com>
Subject: RE: git feature request: git blame --ignore-cleanup/--ignore-trivial
Mime-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

Mathieu Desnoyers wrote:
> Perhaps a new git blame "--ignore-trivial" and/or "--ignore-cleanup" could solve
> this by filtering out "trivial" and "cleanup" patches from the history it considers.

While this feature would be a good addition, more often than not I need
to look behind the latest commit regardless of whether or not it's a
trivial one.

So what I often end up doing is a `git blame --incremental`:

  git blame --incremental -L100,+6 file.c | grep -o -e '^[0-9a-f]\{40\}'

This can be fed to `git log --stdin --oneline --no-walk` for more
user-friendliness.

Of course you could just do:

  git log -L100,+6:file.c --oneline --no-patch

But for some reason that's much slower on my system.

Cheers.

-- 
Felipe Contreras