From: "Virgil Dupras" <vdupras@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoolkit:master commit in: /
Date: Mon, 1 Apr 2019 01:51:22 +0000 (UTC) [thread overview]
Message-ID: <1554083002.7e1e18aeb7e6ab7528dbe09af73c6922cceee091.vdupras@gentoo> (raw)
commit: 7e1e18aeb7e6ab7528dbe09af73c6922cceee091
Author: Virgil Dupras <vdupras <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 1 01:42:44 2019 +0000
Commit: Virgil Dupras <vdupras <AT> gentoo <DOT> org>
CommitDate: Mon Apr 1 01:43:22 2019 +0000
URL: https://gitweb.gentoo.org/proj/gentoolkit.git/commit/?id=7e1e18ae
Updated NEWS for v0.4.{1,2,3}
Signed-off-by: Virgil Dupras <vdupras <AT> gentoo.org>
NEWS | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/NEWS b/NEWS
index 9309ab8..7eacb10 100644
--- a/NEWS
+++ b/NEWS
@@ -1,5 +1,22 @@
News (new features/major bug fixes)
+gentoolkit-0.4.3
+----------------
+ * epkginfo: Add 'reverse' display option for equery
+ * Speed up "equery depends" by a great deal
+ * Fix broken test suite and add new tests
+ * Add tox config
+
+gentoolkit-0.4.2
+----------------
+ * Improve keyword grouping and sorting in eshowkw
+ * Bug fixes in eshowkw
+
+gentoolkit-0.4.1
+----------------
+ * ekeyword: Support sorting keywords without additional changes
+ * Bug fixes in revdep_rebuild, equery, eclean
+
gentoolkit-0.4.0
----------------
* Merge ekeyword, ebump, imlate tools from gentoolkit-dev
next reply other threads:[~2019-04-01 1:51 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 1:51 Virgil Dupras [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-10 2:28 [gentoo-commits] proj/gentoolkit:master commit in: / Matt Turner
2024-05-08 21:43 Sam James
2024-04-25 20:37 Sam James
2024-03-12 21:43 Sam James
2024-03-12 21:43 Sam James
2024-03-12 21:43 Sam James
2024-02-16 20:39 Sam James
2024-01-19 6:37 Sam James
2024-01-19 4:54 Sam James
2024-01-18 20:57 Matt Turner
2024-01-18 20:57 Matt Turner
2023-12-03 7:51 Sam James
2023-03-24 2:50 Sam James
2023-03-20 4:41 Sam James
2022-07-10 20:49 Brian Dolbec
2022-07-10 18:59 Brian Dolbec
2022-07-10 18:41 Brian Dolbec
2022-07-10 17:20 Brian Dolbec
2022-03-16 18:19 Matt Turner
2022-03-16 18:19 Matt Turner
2022-02-09 10:48 Sam James
2021-09-21 21:01 Matt Turner
2021-09-20 23:02 Matt Turner
2021-09-20 22:57 Matt Turner
2021-09-20 22:57 Matt Turner
2021-09-20 22:57 Matt Turner
2021-03-02 3:31 Matt Turner
2020-04-24 8:34 Michał Górny
2020-04-24 8:06 Michał Górny
2020-03-12 16:51 Matt Turner
2020-02-19 5:44 Michał Górny
2020-01-26 15:20 Michał Górny
2019-08-19 3:51 Zac Medico
2019-05-11 23:09 Virgil Dupras
2018-08-14 16:01 Virgil Dupras
2017-03-23 1:40 Mike Frysinger
2017-03-22 20:54 Brian Dolbec
2017-03-22 20:13 Brian Dolbec
2017-03-22 12:51 Brian Dolbec
2016-08-01 4:10 Brian Dolbec
2016-08-01 4:10 Brian Dolbec
2016-03-13 15:11 Mike Gilbert
2015-12-20 20:33 Mike Gilbert
2015-11-24 18:14 Paul Varner
2015-11-24 18:12 Paul Varner
2015-10-15 16:44 Paul Varner
2015-10-15 16:44 Paul Varner
2015-10-15 16:44 Paul Varner
2015-10-15 16:44 Paul Varner
2015-10-15 16:44 Paul Varner
2015-10-15 16:44 Paul Varner
2015-10-15 16:44 Paul Varner
2015-10-15 16:44 Paul Varner
2015-10-15 16:44 Paul Varner
2014-11-03 22:59 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=1554083002.7e1e18aeb7e6ab7528dbe09af73c6922cceee091.vdupras@gentoo \
--to=vdupras@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