lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 02 Jun 2021 16:16:54 -0500
From:   Felipe Contreras <felipe.contreras@...il.com>
To:     Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
        git@...r.kernel.org
Cc:     Peter Zijlstra <peterz@...radead.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Jiri Kosina <trivial@...nel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: RE: git feature request: git blame --ignore-cleanup/--ignore-trivial

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ