On Tue, 11 Feb 2025, Konstantin Ryabitsev wrote:
> On Tue, Feb 11, 2025 at 09:40:24AM -0800, Linus Torvalds wrote:
> > On Tue, 11 Feb 2025 at 08:07, Lee Jones <lee@xxxxxxxxxx> wrote:
> > >
> > > > Out of interest, how did you apply it? b4 was playing up for me.
> >
> > So I had no issues, but I don't actually use b4 to apply the patches,
> > only to fetch them.
> >
> > > Fetching patch(es)
> > > /home/lee/bin/apply-patch.sh: line 134: /tmp/<Z6Ow+T/uSv128wdR@xxxxxxxxxx>.mbox: No such file or directory
> > >
> > > Where apply-patch.sh: line 134:
> > >
> > > b4 am -3 -slt ${PATCHES} -o - ${id} > ${MBOX}
> > >
> > > My first guess would be the stray '/' in the Message-ID.
> >
> > I don't know your apply-patch.sh script, so maybe the bug is there,
> > and it's your MBOX thing that you create without quoting the message
> > ID.
>
> That would be my guess, too, as b4 itself has no trouble fetching or applying
> this series:
>
> $ b4 shazam Z6Ow+T/uSv128wdR@xxxxxxxxxx
> Grabbing thread from lore.kernel.org/all/Z6Ow%2BT%2FuSv128wdR@xxxxxxxxxx/t.mbox.gz
> Analyzing 7 messages in the thread
> Analyzing 0 code-review messages
> Checking attestation on all messages, may take a moment...
> ---
> ✓ [PATCH] MAINTAINERS: Move Pavel to kernel.org address
> ---
> ✓ Signed: DKIM/ucw.cz
> ---
> Total patches: 1
> ---
> Applying: MAINTAINERS: Move Pavel to kernel.org address
I guess it's the fact that I create a file with the name of the
Message-ID which includes the slash. This is the first time I've seen
this happen. I'll investigate locally. Thanks for your time.
--
Lee Jones [李琼斯]
