tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mark Brown" <broonie@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: b4 ty not remembering fetched patches
Date: Fri, 15 May 2020 19:19:18 +0100	[thread overview]
Message-ID: <20200515181918.GO5066@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 386 bytes --]

Hi Konstantin,

When I run 

	b4 am -t 20200515104758.6934-1-Sergey.Semin@baikalelectronics.ru

a mailbox is generated (incomplete due to issues with vger spam
filtering) but the fetched patches are not recorded in the b4 ty
database (as showing by b4 ty -l).  This happens even if only patches
that are present on the list are requested on the command line.

Thanks,
Mark

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 499 bytes --]

             reply	other threads:[~2020-05-15 18:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 18:19 Mark Brown [this message]
2020-05-15 18:36 ` b4 ty not remembering fetched patches Konstantin Ryabitsev
2020-05-15 19:26   ` Mark Brown

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=20200515181918.GO5066@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=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).