From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <fred.w.bacon@gmail.com>, <openembedded-core@lists.openembedded.org>
Cc: "Fred Bacon" <bacon@aerodyne.com>
Subject: Re: [OE-core] [PATCH 0/1] lighttpd: fix trailing '/' on files in dirlisting
Date: Tue, 20 Jan 2026 09:08:46 +0100 [thread overview]
Message-ID: <DFT9HHZDO6T2.NPBC2K7V0JBC@bootlin.com> (raw)
In-Reply-To: <20260119203509.3960946-1-fred.w.bacon@gmail.com>
Hi,
On Mon Jan 19, 2026 at 9:35 PM CET, Fred Bacon via lists.openembedded.org wrote:
> From: Fred Bacon <bacon@aerodyne.com>
>
> Backporting an upstream bug fix for lighttpd's mod_dirlisting.
>
> Fred Bacon (1):
> lighttpd: Fix trailing slash on files in mod_dirlisting
>
> .../lighttpd/0001-mod_dirlisting.patch | 48 +++++++++++++++++++
> .../lighttpd/lighttpd_1.4.74.bb | 1 +
> 2 files changed, 49 insertions(+)
> create mode 100644 meta/recipes-extended/lighttpd/lighttpd/0001-mod_dirlisting.patch
Current version of lighttpd on master is 1.4.82, so this does not apply. Did you
send this for a specific branch of openembedded-core? If so, you need to include
the branch name in the patch subject, as explained here:
https://docs.yoctoproject.org/contributor-guide/submit-changes.html#submitting-changes-to-stable-release-branches
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-01-20 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 20:35 [PATCH 0/1] lighttpd: fix trailing '/' on files in dirlisting fred.w.bacon
2026-01-19 20:35 ` [PATCH 1/1] lighttpd: Fix trailing slash on files in mod_dirlisting fred.w.bacon
2026-01-20 8:08 ` Antonin Godard [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=DFT9HHZDO6T2.NPBC2K7V0JBC@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=bacon@aerodyne.com \
--cc=fred.w.bacon@gmail.com \
--cc=openembedded-core@lists.openembedded.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