From: "Mike Gilbert" <floppym@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] data/gentoo-news:master commit in: 2022-12-01-systemd-usrmerge/
Date: Thu, 1 Dec 2022 20:29:07 +0000 (UTC) [thread overview]
Message-ID: <1669926525.b333b4666182bd4dbfe37df6d3b8010d39d8fded.floppym@gentoo> (raw)
commit: b333b4666182bd4dbfe37df6d3b8010d39d8fded
Author: Mike Gilbert <floppym <AT> gentoo <DOT> org>
AuthorDate: Thu Dec 1 20:28:45 2022 +0000
Commit: Mike Gilbert <floppym <AT> gentoo <DOT> org>
CommitDate: Thu Dec 1 20:28:45 2022 +0000
URL: https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=b333b466
2022-12-01-systemd-usrmerge: add missing colon
Signed-off-by: Mike Gilbert <floppym <AT> gentoo.org>
2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt b/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt
index 78f2871..87ec4af 100644
--- a/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt
+++ b/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt
@@ -1,8 +1,8 @@
Title: /usr merge for systemd users
Author: Mike Gilbert <floppym@gentoo.org>
Posted: 2022-12-01
-Revision: 1
-News-Item-Format 2.0
+Revision: 2
+News-Item-Format: 2.0
Display-If-Installed: sys-apps/systemd
In the latter half of 2023, systemd will drop support for
next reply other threads:[~2022-12-01 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 20:29 Mike Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-06 15:50 [gentoo-commits] data/gentoo-news:master commit in: 2022-12-01-systemd-usrmerge/ Sam James
2022-12-08 16:55 Mike Gilbert
2022-12-05 8:42 Sam James
2022-12-01 18:09 Mike Gilbert
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=1669926525.b333b4666182bd4dbfe37df6d3b8010d39d8fded.floppym@gentoo \
--to=floppym@gentoo.org \
--cc=gentoo-commits@lists.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