From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [PATCH] profiles: update package.mask's header for GLEP 84
Date: Sun, 13 Apr 2025 13:36:06 -0000 (UTC) [thread overview]
Message-ID: <pan$78042$81d4fd5b$52d0d64b$d57d823@cox.net> (raw)
In-Reply-To: 20250412202036.11634-1-alexey+gentoo@asokolov.org
alexey+gentoo posted on Sat, 12 Apr 2025 20:20:38 +0000 as excerpted:
> ## Example:
> ##
> ## # Dev E. Loper <developer@gentoo.org> (2019-07-01)
> -## # Masked for removal in 30 days. Doesn't work
> -## # with new libfoo. Upstream dead, gtk-1, smells
> -## # funny. (bug #987654)
> +## # Doesn't work with new libfoo. Upstream dead, gtk-1, smells
> +## # funny.
> +## # Removal on 2019-08-01. Bug #987654.
> ## app-misc/some-package
OCD triggered:
Two very optional (it's an example after all) suggestions given you're
already changing it:
1) Example-timeliness niggle: s/gtk-1/qt5/ (or pick other appropriate...)
qt5 isn't out-of-tree yet but the effort is toward that /eventually/,
so it's a far more current example than gtk-1. (/How/ long has that been
out-of-tree?)
2) Style niggle: Wrapping a two-word phrase to put just one on a line by
itself... [grumble, grumble]. Sentence line-breaks are even better
so maybe (example in-point, "maybe:" wrapped to its own line...):
> +## # Doesn't work with new libfoo.
> +## # Upstream dead, qt5, smells funny.
(Or maybe with the shorter qt5 it'll all fit on one line?)
Again, both entirely optional, but that /would/ satisfy my OCD. YMMV.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2025-04-13 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 20:20 [gentoo-dev] [PATCH] profiles: update package.mask's header for GLEP 84 alexey+gentoo
2025-04-13 13:36 ` Duncan [this message]
2025-04-14 21:11 ` [gentoo-dev] " Alexey Sokolov
2025-04-15 19:54 ` Sam James
2025-04-15 21:16 ` Alexey Sokolov
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='pan$78042$81d4fd5b$52d0d64b$d57d823@cox.net' \
--to=1i5t5.duncan@cox.net \
--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