From: Lee Jones <lee@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
tools@kernel.org, Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>,
rafael@kernel.org, linux-leds@vger.kernel.org
Subject: Re: MAINTAINERS: Move Pavel to kernel.org address
Date: Wed, 12 Feb 2025 16:00:04 +0000 [thread overview]
Message-ID: <20250212160004.GF2274105@google.com> (raw)
In-Reply-To: <20250211-coral-copperhead-of-dignity-bcb3ce@lemur>
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@kernel.org> 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@duo.ucw.cz>.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@duo.ucw.cz
> Grabbing thread from lore.kernel.org/all/Z6Ow%2BT%2FuSv128wdR@duo.ucw.cz/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 [李琼斯]
prev parent reply other threads:[~2025-02-12 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Z6Ow+T/uSv128wdR@duo.ucw.cz>
[not found] ` <20250211141109.GV1868108@google.com>
[not found] ` <CAHk-=whdcXj==9TkCpQYpmzLweCoDzd9_i8SrODjaQ3ysSe6dw@mail.gmail.com>
[not found] ` <20250211155614.GY1868108@google.com>
[not found] ` <20250211160125.GA2274105@google.com>
2025-02-11 17:40 ` MAINTAINERS: Move Pavel to kernel.org address Linus Torvalds
2025-02-11 18:24 ` Konstantin Ryabitsev
2025-02-12 16:00 ` Lee Jones [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=20250212160004.GF2274105@google.com \
--to=lee@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=tools@kernel.org \
--cc=torvalds@linux-foundation.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).