tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: tools@linux.kernel.org
Subject: Initial "b4 diff" landed in master
Date: Fri, 15 May 2020 18:03:14 -0400	[thread overview]
Message-ID: <20200515220314.z5m5nqpz57mtos7v@chatter.i7.local> (raw)

Hi, all:

Borrowing liberally from Jason's jg_tools, I had a first go at 
implementing "b4 diff". It's pretty slick when it works, for which it 
currently needs to be able to find the exact indexes for the files being 
modified. I found that having linux-next in my remotes helped to get 
most of those blobs into my local tree.

I would be happy if you poke at it some and let me know how it's working 
for you and what output improvements you can suggest.

Example:

$ b4 diff 1587451187-6889-1-git-send-email-masonccyang@mxic.com.tw
Looking up https://lore.kernel.org/r/1587451187-6889-1-git-send-email-masonccyang%40mxic.com.tw
Grabbing thread from lore.kernel.org/linux-mtd
Retrieved 26 messages in the thread
Checking for older revisions on https://lore.kernel.org/linux-mtd/
Added 17 messages from thread: [PATCH 0/4] mtd: spi-nor: Add support for Octal 8D-8D-8D mode
---
Analyzing 45 messages in the thread
Preparing fake-am for v1: spi: spi-mem: Add support for Octal 8D-8D-8D mode
  range: c20efe82ab72..6083ca557825
Preparing fake-am for v2: mtd: spi-nor: Add support for Octal 8D-8D-8D mode
  range: 5eaa5d76ab2e..8bfd7eea5726
---
Success, you may now run:
    git range-diff c20efe82ab72..6083ca557825 5eaa5d76ab2e..8bfd7eea5726


Best,
-K

                 reply	other threads:[~2020-05-15 22:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200515220314.z5m5nqpz57mtos7v@chatter.i7.local \
    --to=konstantin@linuxfoundation.org \
    --cc=tools@linux.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).