From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage-utils:master commit in: man/, man/include/
Date: Sat, 17 Aug 2019 08:37:05 +0000 (UTC) [thread overview]
Message-ID: <1563475126.4b27faa3832c62110573d4fa587a117047bf139c.grobian@gentoo> (raw)
commit: 4b27faa3832c62110573d4fa587a117047bf139c
Author: Fabian Groffen <grobian <AT> gentoo <DOT> org>
AuthorDate: Thu Jul 18 18:38:46 2019 +0000
Commit: Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Thu Jul 18 18:38:46 2019 +0000
URL: https://gitweb.gentoo.org/proj/portage-utils.git/commit/?id=4b27faa3
man/qlop: q -> g
g is now best matched by t, q was never doing anything in particular
Signed-off-by: Fabian Groffen <grobian <AT> gentoo.org>
man/include/qlop.desc | 2 +-
man/qlop.1 | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/man/include/qlop.desc b/man/include/qlop.desc
index 3505173..e39f689 100644
--- a/man/include/qlop.desc
+++ b/man/include/qlop.desc
@@ -21,6 +21,6 @@ After version \fB0.74\fR of portage-utils, \fIqlop\fR was changed
considerably to be more consistent and more advanced. Most notably,
this has changed default date output and commmand line flags. Instead
of reporting the time the operation finished, \fIqlop\fR now reports the
-time the operation started. The behaviour of the old \fB-q\fR flag is
+time the operation started. The behaviour of the old \fB-g\fR flag is
best matched by the new \fB-t\fR flag. Similar, the old \fB-t\fR flag
is matched by the new \fB-a\fR flag.
diff --git a/man/qlop.1 b/man/qlop.1
index 909ebdc..baa5bf5 100644
--- a/man/qlop.1
+++ b/man/qlop.1
@@ -29,7 +29,7 @@ After version \fB0.74\fR of portage-utils, \fIqlop\fR was changed
considerably to be more consistent and more advanced. Most notably,
this has changed default date output and commmand line flags. Instead
of reporting the time the operation finished, \fIqlop\fR now reports the
-time the operation started. The behaviour of the old \fB-q\fR flag is
+time the operation started. The behaviour of the old \fB-g\fR flag is
best matched by the new \fB-t\fR flag. Similar, the old \fB-t\fR flag
is matched by the new \fB-a\fR flag.
.SH OPTIONS
next reply other threads:[~2019-08-17 8:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-17 8:37 Fabian Groffen [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-05 11:29 [gentoo-commits] proj/portage-utils:master commit in: man/, man/include/ Fabian Groffen
2018-04-03 13:56 Fabian Groffen
2018-04-03 12:56 Fabian Groffen
2018-04-03 12:56 Fabian Groffen
2018-04-02 17:27 Fabian Groffen
2018-04-01 13:47 Fabian Groffen
2018-04-01 13:47 Fabian Groffen
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=1563475126.4b27faa3832c62110573d4fa587a117047bf139c.grobian@gentoo \
--to=grobian@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