tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: tools@linux.kernel.org
Cc: users@linux.kernel.org
Subject: Re: [tools] [kernel.org users] What is a useful way to show changes between series?
Date: Wed, 29 Apr 2020 15:47:32 -0400	[thread overview]
Message-ID: <CAMwyc-RaUhw9q9baKKPMLWSWsnQ+e1=+u2yC1Fi2KCGqfTgCtg@mail.gmail.com> (raw)
In-Reply-To: <87sggnexjq.fsf@mpe.ellerman.id.au>

On Wed, 29 Apr 2020 at 00:16, Michael Ellerman <mpe@ellerman.id.au> wrote:
> There will be cases where the diff of the whole series is going to be
> too big and/or busy. So having a way to drill down would be awesome.
>
> The easiest to implement would be limiting it to a single file, which
> would be useful in some cases.

With Jason's help, I think I have a good idea how we can do this. It's
not infallible, but it moves most of the logic to git-range-diff,
which is how I prefer it anyway. I'll try to figure out how to limit
this to a subpath and if I can do it without it potentially causing
more confusion, then I'll try to implement it.

> Harder to implement but possibly more useful would be showing the diff
> between the two series up to some point, so eg. show me the changes
> between the series but only patches 1-5.

Well, the upside of using git-range-diff for the actual comparison is
that it makes it very easy to locate the commits that you're
interested in.

Let me try to put together something that folks can try out and then
we can work iteratively from there.

Thanks for everyone's input.

-K

  parent reply	other threads:[~2020-04-29 19:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 19:29 What is a useful way to show changes between series? Konstantin Ryabitsev
2020-04-28 19:35 ` [kernel.org users] " Jason Gunthorpe
2020-04-28 19:44   ` Konstantin Ryabitsev
2020-04-28 19:55     ` Jason Gunthorpe
2020-04-28 20:24       ` Konstantin Ryabitsev
2020-04-29 16:41       ` [tools] jg expand-am (Was: What is a useful way to show changes between series?) Konstantin Ryabitsev
2020-04-29 17:15         ` Jason Gunthorpe
2020-04-29 17:58           ` Konstantin Ryabitsev
2020-04-29 18:01             ` Jason Gunthorpe
2020-04-29 10:13     ` [kernel.org users] What is a useful way to show changes between series? Mark Brown
2020-04-29 15:00       ` James Bottomley
2020-04-29 15:19         ` Mark Brown
2020-04-29 15:44           ` James Bottomley
2020-04-29 15:51             ` Mark Brown
2020-04-29 17:42       ` Junio C Hamano
2020-04-29 17:50         ` Mark Brown
2020-04-29 17:58           ` Jason Gunthorpe
2020-04-29 18:09             ` Mark Brown
2020-04-29 19:12               ` Jason Gunthorpe
2020-04-29 18:24             ` Konstantin Ryabitsev
2020-04-29  4:16 ` mpe
2020-04-29 10:32   ` Paolo Bonzini
2020-04-29 19:47   ` Konstantin Ryabitsev [this message]
2020-04-29 12:49 ` Pavel Machek

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='CAMwyc-RaUhw9q9baKKPMLWSWsnQ+e1=+u2yC1Fi2KCGqfTgCtg@mail.gmail.com' \
    --to=konstantin@linuxfoundation.org \
    --cc=tools@linux.kernel.org \
    --cc=users@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).