From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:master commit in: man/, /
Date: Fri, 3 Feb 2023 06:34:03 +0000 (UTC) [thread overview]
Message-ID: <1675406039.bde7b6440c6cfbf87776e88fc22313dc0ebbc8ca.sam@gentoo> (raw)
commit: bde7b6440c6cfbf87776e88fc22313dc0ebbc8ca
Author: Philipp Rösner <rndxelement <AT> protonmail <DOT> com>
AuthorDate: Fri Jan 27 22:07:13 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Feb 3 06:33:59 2023 +0000
URL: https://gitweb.gentoo.org/proj/portage.git/commit/?id=bde7b644
portage(5): list volatile option as a separate entry
The volatile option was hidden in the sync-webrsync-verify-signature
entry. Add a separate entry for volatile, specifying its possible
values in the portage(5) man page.
Closes: https://bugs.gentoo.org/888585
Signed-off-by: Philipp Rösner <rndxelement <AT> protonmail.com>
Closes: https://github.com/gentoo/portage/pull/982
Signed-off-by: Sam James <sam <AT> gentoo.org>
NEWS | 2 ++
man/portage.5 | 3 ++-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/NEWS b/NEWS
index b22d4e80f..d81d5823f 100644
--- a/NEWS
+++ b/NEWS
@@ -4,6 +4,8 @@ portage-3.0.45 (UNRELEASED)
Bug fixes:
* gpkg: Handle out-of-space errors (bug #891391).
+* portage(5): List volatile option as a separate entry (bug #888585).
+
portage-3.0.44 (2023-01-15)
--------------
diff --git a/man/portage.5 b/man/portage.5
index c2c92faaa..f722bfb1a 100644
--- a/man/portage.5
+++ b/man/portage.5
@@ -1260,7 +1260,8 @@ Keep snapshots in \fBDISTDIR\fR (do not delete). Defaults to no, false.
Require the detached tarball signature to contain a good OpenPGP
signature. This uses the OpenPGP key(ring) specified by the
sync\-openpgp\-key\-path setting. Defaults to no, false.
-.B volatile
+.TP
+.B volatile = yes|no|true|false
Specifies whether a repository is volatile. Volatile repositories
are assumed to contain changes made outside of Portage. This prohibits
optimizations from occurring by assuming the integrity of the repository
next reply other threads:[~2023-02-03 6:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 6:34 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-14 5:03 [gentoo-commits] proj/portage:master commit in: man/, / Sam James
2022-07-18 20:22 Sam James
2019-08-19 4:51 Zac Medico
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=1675406039.bde7b6440c6cfbf87776e88fc22313dc0ebbc8ca.sam@gentoo \
--to=sam@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