public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "demize" <demize@unstable.systems>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-vcs/jj/
Date: Wed, 21 May 2025 03:15:40 +0000 (UTC)	[thread overview]
Message-ID: <1747797285.6e5c5e60c09284e38beeab7fac90c889c59f65b1.demize@gentoo> (raw)

commit:     6e5c5e60c09284e38beeab7fac90c889c59f65b1
Author:     Vivian Heisz (vhz) <demize <AT> unstable <DOT> systems>
AuthorDate: Tue May 20 15:32:23 2025 +0000
Commit:     demize <demize <AT> unstable <DOT> systems>
CommitDate: Wed May 21 03:14:45 2025 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=6e5c5e60

dev-vcs/jj: add RUST_MIN_VER

Required by jj's MSRV. No revbump, since builds without the
MSRV should have failed, so there's no need to rebuild.

Signed-off-by: Vivian Heisz (vhz) <demize <AT> unstable.systems>

 dev-vcs/jj/jj-0.29.0.ebuild | 2 ++
 dev-vcs/jj/metadata.xml     | 2 +-
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/dev-vcs/jj/jj-0.29.0.ebuild b/dev-vcs/jj/jj-0.29.0.ebuild
index bad33af71..cb93bb337 100644
--- a/dev-vcs/jj/jj-0.29.0.ebuild
+++ b/dev-vcs/jj/jj-0.29.0.ebuild
@@ -5,6 +5,8 @@
 
 EAPI=8
 
+RUST_MIN_VER="1.84.0"
+
 inherit cargo
 
 DESCRIPTION="Jujutsu - an experimental version control system"

diff --git a/dev-vcs/jj/metadata.xml b/dev-vcs/jj/metadata.xml
index f0f1985eb..dd6497b6a 100644
--- a/dev-vcs/jj/metadata.xml
+++ b/dev-vcs/jj/metadata.xml
@@ -2,7 +2,7 @@
 <!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
 <pkgmetadata>
   <maintainer type="person">
-    <name>Vivian Heisz (demize)</name>
+    <name>Vivian Heisz (vhz)</name>
     <email>demize@unstable.systems</email>
   </maintainer>
   <upstream>


             reply	other threads:[~2025-05-21  3:15 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-21  3:15 demize [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-08 15:19 [gentoo-commits] repo/proj/guru:dev commit in: dev-vcs/jj/ demize
2025-05-08 15:19 demize
2025-04-21 18:18 demize
2025-04-07 18:10 demize
2025-04-05 13:18 demize
2025-03-08 17:26 demize
2025-03-07  3:32 demize
2025-03-07  3:32 demize
2025-03-07  3:32 demize
2025-03-07  3:32 demize
2025-03-06  3:17 demize
2025-03-06  3:17 demize
2025-02-10 19:56 demize
2025-02-10 19:56 demize
2025-01-28 15:19 demize
2025-01-28 15:19 demize
2025-01-28 15:19 demize
2024-12-15 23:30 Marco Rebhan
2024-11-09 11:58 Steffen Winter
2024-11-09 11:58 Steffen Winter
2024-09-12  8:49 Steffen Winter
2024-09-12  8:45 Steffen Winter
2024-09-07 11:29 Steffen Winter
2024-09-07 11:29 Steffen Winter
2024-08-23 17:27 Steffen Winter
2024-08-23 17:27 Steffen Winter
2024-08-23 17:27 Steffen Winter
2024-07-06 11:02 Steffen Winter
2024-06-10 18:35 Steffen Winter
2024-06-10 18:35 Steffen Winter
2024-05-22 12:15 Steffen Winter
2024-05-22 12:15 Steffen Winter
2024-05-22 12:00 Steffen Winter
2024-05-07 17:19 Steffen Winter
2024-05-01 17:52 Steffen Winter
2024-04-08 16:49 Steffen Winter
2024-04-08 16:49 Steffen Winter
2024-04-07  9:49 Steffen Winter
2024-03-26 11:21 Steffen Winter
2024-03-26 11:20 Steffen Winter

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=1747797285.6e5c5e60c09284e38beeab7fac90c889c59f65b1.demize@gentoo \
    --to=demize@unstable.systems \
    --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