From: hasufell <hasufell@gentoo.org>
To: "Anthony G. Basile" <blueness@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [gentoo-commits] data/gentoo-news:master commit in: 2015-10-21-future-support-of-hardened-sources-kernel/
Date: Sat, 24 Oct 2015 00:45:34 +0200 [thread overview]
Message-ID: <562AB88E.10701@gentoo.org> (raw)
In-Reply-To: <1445391643.1ff602d951b09029917bcc5bf391cbe390772a7b.blueness@gentoo>
On 10/21/2015 03:34 AM, Anthony G. Basile wrote:
> commit: 1ff602d951b09029917bcc5bf391cbe390772a7b
> Author: Anthony G. Basile <blueness <AT> gentoo <DOT> org>
> AuthorDate: Wed Oct 21 01:31:55 2015 +0000
> Commit: Anthony G. Basile <blueness <AT> gentoo <DOT> org>
> CommitDate: Wed Oct 21 01:40:43 2015 +0000
> URL: https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=1ff602d9
>
> News item regarding future support of hardened-sources kernels.
>
> ...uture-support-of-hardened-sources-kernel.en.txt | 63 ++++++++++++++++++++++
> ...e-support-of-hardened-sources-kernel.en.txt.asc | 17 ++++++
> 2 files changed, 80 insertions(+)
>
> diff --git a/2015-10-21-future-support-of-hardened-sources-kernel/2015-10-21-future-support-of-hardened-sources-kernel.en.txt b/2015-10-21-future-support-of-hardened-sources-kernel/2015-10-21-future-support-of-hardened-sources-kernel.en.txt
> new file mode 100644
> index 0000000..f421440
> --- /dev/null
> +++ b/2015-10-21-future-support-of-hardened-sources-kernel/2015-10-21-future-support-of-hardened-sources-kernel.en.txt
> @@ -0,0 +1,63 @@
> +Title: Future Support of hardened-sources Kernel
> +Content-Type: text/plain
> +Posted: 2015-10-21
> +Revision: 1
> +News-Item-Format: 1.0
[...]
This news item is missing an Author header, causing my PM to throw warnings.
GLEP42 also says it is a mandatory header.
https://wiki.gentoo.org/wiki/GLEP:42#News_Item_Headers
parent reply other threads:[~2015-10-23 22:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1445391643.1ff602d951b09029917bcc5bf391cbe390772a7b.blueness@gentoo>]
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=562AB88E.10701@gentoo.org \
--to=hasufell@gentoo.org \
--cc=blueness@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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