From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/nginx: fix NGINX pidfile handling systemd
Date: Fri, 28 May 2021 18:42:33 +0200 [thread overview]
Message-ID: <87czta24jq.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1b2fee92-2752-c02d-93a3-6ad716ca5259@mind.be> (Arnout Vandecappelle's message of "Fri, 28 May 2021 18:10:29 +0200")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
>> Yes, I agree. We already have a section in the manual for it:
>>
>> https://github.com/nginxinc/docker-nginx/blob/master/Dockerfile-debian.template#L106
> I think you meant
> https://buildroot.org/downloads/manual/manual.html#migrating-from-ol-versions
Hah, indeed ;)
>> But very little content :/ Patches accepted!
> What I meant is: we should require an update of that section whenever there's a
> potentially breaking change. From 2021.05-rc1, for example:
> FORTIFY_SOURCE, PIC/PIE, RELRO and SSP security hardening
> options are now enabled by default.
> The change of the default could have updated that section in the same patch.
Yes, I agree. I will try to remind contributors in the future.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2021-05-28 16:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 14:41 [Buildroot] [PATCH] package/nginx: fix NGINX pidfile handling systemd Matthew Weber
2021-05-26 20:48 ` Yann E. MORIN
2021-05-27 20:49 ` Arnout Vandecappelle
2021-05-28 11:39 ` Yann E. MORIN
2021-05-28 11:51 ` Arnout Vandecappelle
2021-05-28 13:12 ` Yann E. MORIN
2021-05-28 13:24 ` Arnout Vandecappelle
2021-05-28 15:48 ` Peter Korsgaard
2021-05-28 16:10 ` Arnout Vandecappelle
2021-05-28 16:42 ` Peter Korsgaard [this message]
2021-05-28 15:46 ` Peter Korsgaard
2021-05-28 16:05 ` Arnout Vandecappelle
2021-05-28 19:41 ` Yann E. MORIN
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=87czta24jq.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.