Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: tools@linux.kernel.org
Subject: "b4 ty -d all" crash
Date: Mon, 17 Oct 2022 12:23:23 -0500	[thread overview]
Message-ID: <20221017172323.GA3715117@bhelgaas> (raw)

I've used "b4 am" for a long time, but I'm a first-time and naive
"b4 ty" user:

  12:17:52 ~/linux (for-linus)$ b4 ty -d all
  Discarding 707 messages
    Discarded: [PATCH 0/5] Handled return value of platform_get_irq correctly
  Traceback (most recent call last):
    File "/home/bjorn/.local/bin/b4", line 8, in <module>
      sys.exit(cmd())
    File "/home/bjorn/.local/lib/python3.8/site-packages/b4/command.py", line 341, in cmd
      cmdargs.func(cmdargs)
    File "/home/bjorn/.local/lib/python3.8/site-packages/b4/command.py", line 106, in cmd_ty
      b4.ty.main(cmdargs)
    File "/home/bjorn/.local/lib/python3.8/site-packages/b4/ty.py", line 678, in main
      discard_selected(cmdargs)
    File "/home/bjorn/.local/lib/python3.8/site-packages/b4/ty.py", line 578, in discard_selected
      msgids.append(pdata[2])
  IndexError: list index out of range

  12:18:06 ~/linux (for-linus)$ b4 --version
  0.10.1

  12:18:29 ~/linux (for-linus)$ b4 ty -l
  Currently tracking:
    1: [PATCH RFC 0/2] pci: Make return value of pcie_capability_*() consistent
	 From: refactormyself@gmail.com <refactormyself@gmail.com>
	 Date: Mon, 4 May 2020 07:18:10 +0200
	 Link: https://lore.kernel.org/r/20200504051812.22662-1-refactormyself@gmail.com
    2: [PATCH v7 0/2] Adding support for Versal CPM as Root Port driver
	 From: Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>
	 Date: Thu, 7 May 2020 17:28:34 +0530
	 Link: https://lore.kernel.org/r/1588852716-23132-1-git-send-email-bharat.kumar.gogada@xilinx.com
  ...
  706: [PATCH] Revert "PCI: tegra: Use PCI_CONF1_EXT_ADDRESS() macro"
	 From: Jon Hunter <jonathanh@nvidia.com>
	 Date: Mon, 17 Oct 2022 09:40:06 +0100
	 Link: https://lore.kernel.org/r/20221017084006.11770-1-jonathanh@nvidia.com
  ---
  You can send them using number ranges, e.g:
    b4 ty -t 1-3,5,7-


             reply	other threads:[~2022-10-17 17:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17 17:23 Bjorn Helgaas [this message]
2022-10-17 20:22 ` "b4 ty -d all" crash Konstantin Ryabitsev
2022-10-17 21:22   ` Bjorn Helgaas

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=20221017172323.GA3715117@bhelgaas \
    --to=helgaas@kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).