From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Konstantin Ryabitsev <mricon@kernel.org>
Cc: tools@linux.kernel.org
Subject: Re: [BUG] b4 can't grap thread with already-percent-encoded slash
Date: Tue, 24 Nov 2020 09:49:41 -0500 [thread overview]
Message-ID: <8a1500fe-7c1a-2904-7723-8e638f524c03@gmail.com> (raw)
In-Reply-To: <20201124144542.arws25irjgylbrqa@chatter.i7.local>
Hi Konstantin,
On 20-11-24 09 h 45, Konstantin Ryabitsev wrote:
> On Tue, Nov 24, 2020 at 09:37:54AM -0500, Philippe Blain wrote:
>> Hello,
>>
>> I tried to use b4 to import this thread:
>> https://lore.kernel.org/git/X7y+cZ3MPqqmGXx%2F@coredump.intra.peff.net/T/#t
>>
>> using that exact URL:
>>
>> b4 mbox -o- https://lore.kernel.org/git/X7y+cZ3MPqqmGXx%2F@coredump.intra.peff.net/T/#t
>>
>> It does not work - I get a 404. I think it's partly
>> due to the already-percent-encoded slash (just before the @).
>> I tried a few things, like manually changing the '%2F' to '/',
>> removing the '/T/#t' suffix, adding '-p git' to disambiguate,
>> but to no avail. I always get either a 404 or "That message-id is not
>> known."
>
> Yes, I kept meaning to fix that -- thanks for the reminder. The latest
> master/stable-0.5.y have a fix for that.
Not sure if you mean that it should be fixed in master... I installed b4 using
pip3 install --user --upgrade git+https://git.kernel.org/pub/scm/utils/b4/b4.git#egg=b4
so I'm at version 0.6.0-dev. Is it supposed to
work ?
Thanks for the quick answer,
Philippe.
next prev parent reply other threads:[~2020-11-24 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 14:37 [BUG] b4 can't grap thread with already-percent-encoded slash Philippe Blain
2020-11-24 14:45 ` Konstantin Ryabitsev
2020-11-24 14:49 ` Philippe Blain [this message]
2020-11-24 14:52 ` Konstantin Ryabitsev
2020-11-24 14:55 ` Philippe Blain
2020-11-24 15:58 ` Konstantin Ryabitsev
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=8a1500fe-7c1a-2904-7723-8e638f524c03@gmail.com \
--to=levraiphilippeblain@gmail.com \
--cc=mricon@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 NNTP newsgroup(s).