From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Kevin Hilman <khilman@baylibre.com>, workflows@vger.kernel.org
Subject: Re: get-lore-mbox: quickly grab full threads from lore
Date: Mon, 17 Feb 2020 11:52:55 +0100 [thread overview]
Message-ID: <CAMuHMdU4B8JRnyuPmJ5jKryJj580OQnFYWXo8FXpwdFe7wnvxg@mail.gmail.com> (raw)
In-Reply-To: <7hftfcaow6.fsf@baylibre.com>
Hi Konstantin,
On Fri, Feb 14, 2020 at 9:36 PM Kevin Hilman <khilman@baylibre.com> wrote:
> Anyways, this tool is really great and it's already replacing some of my
> homebrew scripts.
Indeed, thanks a lot!
BTW, I found another issue: 20200118124856.GA3421@nishad produces
a backtrace when using the "-a" option.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2020-02-17 10:53 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
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 [this message]
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=CAMuHMdU4B8JRnyuPmJ5jKryJj580OQnFYWXo8FXpwdFe7wnvxg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=khilman@baylibre.com \
--cc=konstantin@linuxfoundation.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 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).