From: "Mark Brown" <broonie@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: Re: b4 ty not remembering fetched patches
Date: Fri, 15 May 2020 20:26:34 +0100 [thread overview]
Message-ID: <20200515192634.GR5066@sirena.org.uk> (raw)
In-Reply-To: <20200515183602.ivwwyxafxojmc7mp@chatter.i7.local>
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
On Fri, May 15, 2020 at 02:36:02PM -0400, Konstantin Ryabitsev wrote:
> On Fri, May 15, 2020 at 07:19:18PM +0100, Mark Brown wrote:
> > 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.
> Right, this was intentional due to trying to be over-cautious. If we
> don't have the complete thread, then we probably shouldn't be tracking
> if this incomplete thread was applied or not -- at least that was my
> thinking. What is your thoughts on that?
I think that's a sensible decision and wasn't particularly surprised by
that bit of it. In fact what might be handy would be an option to not
output the partial mailbox if we can't find some of the patches - that'd
help spot problems early on in the process.
> Of course, if we're specifically selecting a subset of that thread, we
> shouldn't be applying that logic. I'll see if I can add that caveat in.
Right, I'd have expected it to only apply to whatever was explicitly
asked for.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 499 bytes --]
prev parent reply other threads:[~2020-05-15 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 18:19 b4 ty not remembering fetched patches Mark Brown
2020-05-15 18:36 ` Konstantin Ryabitsev
2020-05-15 19:26 ` Mark Brown [this message]
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=20200515192634.GR5066@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).