From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-debug/gdb/
Date: Sun, 1 Dec 2024 08:53:00 +0000 (UTC) [thread overview]
Message-ID: <1733043107.13e92531b953583d1f5049fbed2c68645f6f968c.sam@gentoo> (raw)
commit: 13e92531b953583d1f5049fbed2c68645f6f968c
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Dec 1 08:51:37 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Dec 1 08:51:47 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=13e92531
dev-debug/gdb: add mirrors to EGIT_REPO_URI
sourceware was down earlier, so add some mirrors.
sourcehut is an official mirror (albeit an experiment IIRC) by sourceware
and x86-binutils is run by H.J. Lu.
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-debug/gdb/gdb-9999.ebuild | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/dev-debug/gdb/gdb-9999.ebuild b/dev-debug/gdb/gdb-9999.ebuild
index 811789dab6d8..039c98a9e0ca 100644
--- a/dev-debug/gdb/gdb-9999.ebuild
+++ b/dev-debug/gdb/gdb-9999.ebuild
@@ -23,7 +23,11 @@ is_cross() { [[ ${CHOST} != ${CTARGET} ]] ; }
case ${PV} in
9999*)
# live git tree
- EGIT_REPO_URI="https://sourceware.org/git/binutils-gdb.git"
+ EGIT_REPO_URI="
+ https://sourceware.org/git/binutils-gdb.git
+ https://git.sr.ht/~sourceware/binutils-gdb
+ https://gitlab.com/x86-binutils/binutils-gdb.git
+ "
inherit git-r3
SRC_URI=""
;;
next reply other threads:[~2024-12-01 8:53 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-01 8:53 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-26 2:22 [gentoo-commits] repo/gentoo:master commit in: dev-debug/gdb/ Sam James
2025-04-26 2:22 Sam James
2025-04-26 2:22 Sam James
2025-04-26 2:22 Sam James
2025-04-26 2:22 Sam James
2025-04-26 2:22 Sam James
2025-04-26 2:22 Sam James
2025-04-26 2:22 Sam James
2025-04-21 8:35 Sam James
2025-04-21 7:56 Sam James
2025-04-21 7:51 Sam James
2025-04-21 7:43 Sam James
2025-04-20 22:56 Sam James
2025-04-17 19:36 Fabian Groffen
2025-03-24 0:33 Sam James
2025-03-17 21:00 Sam James
2025-02-22 9:23 Arthur Zamarin
2025-02-13 10:01 Sam James
2025-02-09 18:30 Sam James
2025-02-09 18:30 Sam James
2025-02-09 11:37 Jakov Smolić
2025-02-09 11:37 Jakov Smolić
2025-02-09 11:37 Jakov Smolić
2025-02-09 11:37 Jakov Smolić
2025-02-09 7:17 Sam James
2025-02-06 1:39 Sam James
2025-01-18 12:09 Sam James
2024-11-30 13:37 Sam James
2024-11-30 2:15 Sam James
2024-11-23 13:56 Sam James
2024-11-19 14:10 Sam James
2024-11-19 14:10 Sam James
2024-11-13 3:50 Sam James
2024-11-08 11:57 Sam James
2024-11-08 10:59 Sam James
2024-11-08 6:31 Sam James
2024-11-08 3:54 Sam James
2024-10-27 18:19 Andreas K. Hüttel
2024-10-18 17:32 Arthur Zamarin
2024-10-15 12:47 Arthur Zamarin
2024-10-14 0:50 Sam James
2024-10-14 0:50 Sam James
2024-10-14 0:16 Sam James
2024-10-14 0:16 Sam James
2024-10-13 23:50 Sam James
2024-10-03 9:35 Sam James
2024-09-29 21:05 Sam James
2024-09-29 21:05 Sam James
2024-07-21 13:04 Fabian Groffen
2024-07-17 5:56 Sam James
2024-07-17 5:56 Sam James
2024-07-17 5:56 Sam James
2024-07-17 5:17 Sam James
2024-07-17 5:16 Sam James
2024-07-17 4:59 Sam James
2024-07-17 4:56 Sam James
2024-07-08 3:32 Sam James
2024-06-02 0:14 Sam James
2024-05-11 15:19 Sam James
2024-04-25 23:10 Sam James
2024-04-25 23:10 Sam James
2024-04-25 22:18 Sam James
2024-04-25 22:18 Sam James
2024-04-25 22:18 Sam James
2024-04-25 22:18 Sam James
2024-04-25 22:18 Sam James
2024-03-04 10:24 Sam James
2024-03-03 7:02 Sam James
2024-02-25 9:38 Fabian Groffen
2024-02-20 7:45 Sam James
2024-02-20 7:45 Sam James
2024-02-20 7:45 Sam James
2024-02-20 7:22 Sam James
2024-02-20 7:22 Sam James
2024-02-20 5:56 Sam James
2024-02-20 5:56 Sam James
2024-02-20 5:56 Sam James
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=1733043107.13e92531b953583d1f5049fbed2c68645f6f968c.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