Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "Noralf Trønnes" <noralf@tronnes.org>
Cc: tools@linux.kernel.org
Subject: Re: Error using b4 web endpoint (was Re: git send-email friendly smtp provider anyone?)
Date: Thu, 1 Dec 2022 09:42:47 -0500	[thread overview]
Message-ID: <CAMwyc-SbsFQyA8tTNbqzRkn+wDeo6ELrnV0ngwsx_6M4maHnPA@mail.gmail.com> (raw)
In-Reply-To: <20221130193952.twllu74eduajrauj@meerkat.local>

On Wed, 30 Nov 2022 at 14:39, Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
>
> On Wed, Nov 30, 2022 at 08:34:45PM +0100, Noralf Trønnes wrote:
> > Thanks, working now:
> >
> > https://lore.kernel.org/dri-devel/20221122-gud-shadow-plane-v2-0-435037990a83@tronnes.org/T/#t
>
> Great. There's still some weird annoying stuff with encoding happening, but it
> shouldn't really interfere with anything. You're a great testcase because you
> have 8bit content in many headers of the message and it's tripping up a lot of
> my assumptions about how Python would handle things internally.

For the record, this helped identify a bug in Python:
https://github.com/python/cpython/issues/99927

I'll have to work around it in b4, unfortunately, as even if it's
fixed in 3.11, I'm not sure it'll be backported properly to earlier
versions.

-K

      parent reply	other threads:[~2022-12-01 14:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1bc45775-0667-01f8-36e1-9f65d3081092@tronnes.org>
     [not found] ` <20221121151922.jaal6ym7z2ejju4q@houat>
     [not found]   ` <de12952f-8346-8995-236d-69dcb70f19f6@tronnes.org>
     [not found]     ` <20221122155122.edxtmsqpjxgj4dsj@meerkat.local>
     [not found]       ` <3b06dfd5-0eb4-dbfc-6ba8-077b1a92865b@tronnes.org>
     [not found]         ` <20221122185001.q6hmeblp64jqdzvz@meerkat.local>
     [not found]           ` <02bc2442-e3b3-d720-9d13-ffcdfd760fb8@tronnes.org>
2022-11-22 19:44             ` Error using b4 web endpoint (was Re: git send-email friendly smtp provider anyone?) Konstantin Ryabitsev
2022-11-22 19:48               ` Noralf Trønnes
2022-11-22 20:00                 ` Konstantin Ryabitsev
2022-11-22 20:10                   ` Noralf Trønnes
2022-11-22 20:20                     ` Konstantin Ryabitsev
2022-11-22 20:26                       ` Noralf Trønnes
2022-11-22 20:44                         ` Konstantin Ryabitsev
2022-11-22 21:03                           ` Noralf Trønnes
2022-11-22 21:14                             ` Konstantin Ryabitsev
2022-11-22 22:05                             ` Konstantin Ryabitsev
2022-11-30 16:17                             ` Noralf Trønnes
2022-11-30 16:55                               ` Konstantin Ryabitsev
2022-11-30 17:02                                 ` Noralf Trønnes
2022-11-30 19:17                                   ` Konstantin Ryabitsev
2022-11-30 19:34                                     ` Noralf Trønnes
2022-11-30 19:39                                       ` Konstantin Ryabitsev
2022-11-30 19:59                                         ` Noralf Trønnes
2022-12-01 14:42                                         ` Konstantin Ryabitsev [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=CAMwyc-SbsFQyA8tTNbqzRkn+wDeo6ELrnV0ngwsx_6M4maHnPA@mail.gmail.com \
    --to=konstantin@linuxfoundation.org \
    --cc=noralf@tronnes.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).