public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoolkit:master commit in: /
Date: Fri, 19 Jan 2024 06:37:26 +0000 (UTC)	[thread overview]
Message-ID: <1705646209.a7846cf9dc41f03559f64f4ae8b118868197e316.sam@gentoo> (raw)

commit:     a7846cf9dc41f03559f64f4ae8b118868197e316
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 19 06:36:49 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Jan 19 06:36:49 2024 +0000
URL:        https://gitweb.gentoo.org/proj/gentoolkit.git/commit/?id=a7846cf9

NEWS, meson.build: prepare for gentoolkit-0.6.5

Signed-off-by: Sam James <sam <AT> gentoo.org>

 NEWS        | 4 ++++
 meson.build | 2 +-
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/NEWS b/NEWS
index 7d8b7d0..f3bd744 100644
--- a/NEWS
+++ b/NEWS
@@ -1,5 +1,9 @@
 News (new features/major bug fixes)
 
+gentoolkit-0.6.5
+----------------
+  * eclean: fix eclean-dist with no git3-src dir (bug #922455)
+
 gentoolkit-0.6.4
 ----------------
   * Raise portage requirement to >=3.0.57

diff --git a/meson.build b/meson.build
index 109fa82..c771738 100644
--- a/meson.build
+++ b/meson.build
@@ -1,7 +1,7 @@
 project(
     'gentoolkit',
     'c',
-    version : '0.6.4',
+    version : '0.6.5',
     license : 'GPL-2.0-or-later',
     meson_version : '>=0.64.0'
 )


             reply	other threads:[~2024-01-19  6:37 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19  6:37 Sam James [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  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
2019-04-01  1:51 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=1705646209.a7846cf9dc41f03559f64f4ae8b118868197e316.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