From: Kees Cook <keescook@chromium.org>
To: workflows@vger.kernel.org
Subject: Re: get-lore-mbox: quickly grab full threads from lore
Date: Sat, 1 Feb 2020 09:43:04 -0800 [thread overview]
Message-ID: <202002010941.B3F47C3A1@keescook> (raw)
In-Reply-To: <20200201030105.k6akvbjpmlpcuiky@chatter.i7.local>
On Fri, Jan 31, 2020 at 10:01:05PM -0500, Konstantin Ryabitsev wrote:
> You can see that the git command it gives you has a different branch and
> parent info, which should let you do an easy diff between two branches,
> one using v6, and the other using v7 versions.
I love it -- I've been missing this between gerrit and patchwork, and
now I don't need a GUI at all. :)
> Please give it a try and let me know your feedback! You can find it here:
> https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git/tree/get-lore-mbox.py
>
> It's a bit raw around the edges and I keep finding corner-cases, so it
> would be super interesting for me to get input from people actually
> trying to use it for managing patch series.
I'll give it a spin; thanks!
--
Kees Cook
next prev parent reply other threads:[~2020-02-01 17:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 3:01 get-lore-mbox: quickly grab full threads from lore Konstantin Ryabitsev
2020-02-01 17:43 ` Kees Cook [this message]
2020-02-03 22:38 ` Dan Williams
2020-02-14 19:30 ` Kevin Hilman
2020-02-14 19:40 ` Toke Høiland-Jørgensen
2020-02-14 19:53 ` Mark Brown
2020-02-14 19:53 ` Konstantin Ryabitsev
2020-02-14 20:35 ` Kevin Hilman
2020-02-17 10:52 ` Geert Uytterhoeven
2020-02-17 14:30 ` Konstantin Ryabitsev
2020-02-24 17:39 ` Rob Herring
2020-02-24 18:10 ` Konstantin Ryabitsev
2020-02-15 22:23 ` mbox-export-patch, notmuch-export-patch Sean Whitton
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=202002010941.B3F47C3A1@keescook \
--to=keescook@chromium.org \
--cc=workflows@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.