From: "Nick Sarnie" <sarnex@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-emulation/wine-d3d9/
Date: Sat, 29 Dec 2018 21:17:55 +0000 (UTC) [thread overview]
Message-ID: <1546118176.3c1843a50e50e4821e806ed724e52b971ea6fca6.sarnex@gentoo> (raw)
commit: 3c1843a50e50e4821e806ed724e52b971ea6fca6
Author: Nick Sarnie <sarnex <AT> gentoo <DOT> org>
AuthorDate: Sat Dec 29 21:16:16 2018 +0000
Commit: Nick Sarnie <sarnex <AT> gentoo <DOT> org>
CommitDate: Sat Dec 29 21:16:16 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3c1843a5
app-emulation/wine-d3d9: Sync with ::wine
Add alternative source
Package-Manager: Portage-2.3.53, Repoman-2.3.12
Signed-off-by: Nick Sarnie <sarnex <AT> gentoo.org>
app-emulation/wine-d3d9/wine-d3d9-9999.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-emulation/wine-d3d9/wine-d3d9-9999.ebuild b/app-emulation/wine-d3d9/wine-d3d9-9999.ebuild
index fb4d194b4fb..3ebab9ae1cb 100644
--- a/app-emulation/wine-d3d9/wine-d3d9-9999.ebuild
+++ b/app-emulation/wine-d3d9/wine-d3d9-9999.ebuild
@@ -12,7 +12,7 @@ MY_PN="${PN%%-*}"
MY_P="${MY_PN}-${PV}"
if [[ ${PV} == "9999" ]] ; then
- EGIT_REPO_URI="https://source.winehq.org/git/wine.git"
+ EGIT_REPO_URI="https://source.winehq.org/git/wine.git https://github.com/wine-mirror/wine.git"
EGIT_BRANCH="master"
inherit git-r3
SRC_URI=""
next reply other threads:[~2018-12-29 21:17 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-29 21:17 Nick Sarnie [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-22 20:25 [gentoo-commits] repo/gentoo:master commit in: app-emulation/wine-d3d9/ Nick Sarnie
2019-08-18 12:37 David Seifert
2019-05-12 14:13 Nick Sarnie
2019-02-18 15:44 Nick Sarnie
2019-02-18 15:44 Nick Sarnie
2019-01-27 17:14 Nick Sarnie
2019-01-24 2:44 Nick Sarnie
2019-01-24 2:44 Nick Sarnie
2018-11-25 16:58 Nick Sarnie
2018-11-25 16:58 Nick Sarnie
2018-11-11 17:37 Nick Sarnie
2018-11-11 17:37 Nick Sarnie
2018-11-04 21:06 Nick Sarnie
2018-11-04 21:06 Nick Sarnie
2018-10-13 15:59 Nick Sarnie
2018-10-13 15:59 Nick Sarnie
2018-09-30 19:59 Nick Sarnie
2018-09-30 19:59 Nick Sarnie
2018-09-17 1:16 Nick Sarnie
2018-09-17 1:16 Nick Sarnie
2018-09-02 14:41 Nick Sarnie
2018-09-02 14:41 Nick Sarnie
2018-09-02 1:10 Nick Sarnie
2018-09-01 16:45 Nick Sarnie
2018-08-02 2:44 Nick Sarnie
2018-07-21 17:08 Nick Sarnie
2018-07-21 17:08 Nick Sarnie
2018-07-14 2:47 Nick Sarnie
2018-07-14 2:47 Nick Sarnie
2018-06-24 18:15 Nick Sarnie
2018-06-24 18:15 Nick Sarnie
2018-06-17 19:15 Nick Sarnie
2018-06-17 19:15 Nick Sarnie
2018-05-28 16:02 Nick Sarnie
2018-05-27 16:56 Nick Sarnie
2018-05-27 16:56 Nick Sarnie
2018-05-13 14:47 Nick Sarnie
2018-05-13 14:47 Nick Sarnie
2018-05-02 1:33 Nick Sarnie
2018-05-02 1:33 Nick Sarnie
2018-04-22 19:26 Nick Sarnie
2018-03-02 2:14 NP Hardass
2018-01-22 22:51 NP Hardass
2018-01-22 22:51 NP Hardass
2018-01-20 8:00 NP Hardass
2018-01-20 8:00 NP Hardass
2018-01-05 18:10 Ulrich Müller
2018-01-05 17:02 Ulrich Müller
2017-12-04 6:27 NP Hardass
2017-11-29 2:30 NP Hardass
2017-11-28 16:24 NP Hardass
2017-11-10 19:02 NP Hardass
2017-11-05 5:53 NP Hardass
2017-11-05 5:53 NP Hardass
2017-11-05 5:53 NP Hardass
2017-09-30 20:32 NP Hardass
2017-09-29 3:07 NP Hardass
2017-09-24 16:10 NP Hardass
2017-09-24 16:10 NP Hardass
2017-09-13 21:09 NP Hardass
2017-09-13 19:48 NP Hardass
2017-09-13 19:48 NP Hardass
2017-09-13 19:48 NP Hardass
2017-09-13 19:48 NP Hardass
2017-09-13 19:48 NP Hardass
2017-08-23 18:08 Michał Górny
2017-07-17 21:09 NP Hardass
2017-07-10 1:22 NP Hardass
2017-07-10 1:22 NP Hardass
2017-06-01 1:19 NP Hardass
2017-06-01 1:19 NP Hardass
2017-05-13 1:03 NP Hardass
2017-05-04 5:40 NP Hardass
2017-04-21 6:03 NP Hardass
2017-04-21 6:03 NP Hardass
2017-04-12 1:37 NP Hardass
2017-04-11 11:46 NP Hardass
2017-04-10 19:44 NP Hardass
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=1546118176.3c1843a50e50e4821e806ed724e52b971ea6fca6.sarnex@gentoo \
--to=sarnex@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