From: Adrian Bunk <bunk@stusta.de>
To: Zang Ruochen <zangrc.fnst@cn.fujitsu.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] lighttpd:upgrade 1.4.53 -> 1.4.54
Date: Tue, 18 Jun 2019 14:01:20 +0300 [thread overview]
Message-ID: <20190618110120.GA10836@localhost> (raw)
In-Reply-To: <20190618034219.13116-1-zangrc.fnst@cn.fujitsu.com>
WARNING: lighttpd-1.4.54-r0 do_patch: Fuzz detected:
Applying patch mod-eke-prio.patch
patching file src/Makefile.am
Hunk #1 succeeded at 419 with fuzz 2 (offset 15 lines).
patching file src/mod_eke_prio.c
The context lines in the patches can be updated with devtool:
devtool modify lighttpd
devtool finish --force-patch-refresh lighttpd <layer_path>
Don't forget to review changes done by devtool!
WARNING: lighttpd-1.4.54-r0 do_patch: QA Issue: Patch log indicates that
patches do not apply cleanly. [patch-fuzz]
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2019-06-18 11:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 3:42 [PATCH] lighttpd:upgrade 1.4.53 -> 1.4.54 Zang Ruochen
2019-06-18 11:01 ` Adrian Bunk [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=20190618110120.GA10836@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=zangrc.fnst@cn.fujitsu.com \
/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