From: "NP Hardass" <np-hardass@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/wine:master commit in: app-emulation/wine-d3d9/
Date: Mon, 22 Jan 2018 22:51:09 +0000 (UTC) [thread overview]
Message-ID: <1516495827.12da1b95122afc023812e115118d1cef3e4a6949.np-hardass@gentoo> (raw)
commit: 12da1b95122afc023812e115118d1cef3e4a6949
Author: NP-Hardass <NP-Hardass <AT> gentoo <DOT> org>
AuthorDate: Sat Jan 20 08:12:31 2018 +0000
Commit: NP Hardass <np-hardass <AT> gentoo <DOT> org>
CommitDate: Sun Jan 21 00:50:27 2018 +0000
URL: https://gitweb.gentoo.org/repo/proj/wine.git/commit/?id=12da1b95
app-emulation/wine-d3d9: Add maintainer description/warning
Original edits should not take place in ::gentoo. All development
takes place in ::wine where many more versions than are kept in ::gentoo
are kept in sync.
Package-Manager: Portage-2.3.19, Repoman-2.3.6
app-emulation/wine-d3d9/metadata.xml | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/app-emulation/wine-d3d9/metadata.xml b/app-emulation/wine-d3d9/metadata.xml
index 44e32fc..375e226 100644
--- a/app-emulation/wine-d3d9/metadata.xml
+++ b/app-emulation/wine-d3d9/metadata.xml
@@ -4,6 +4,10 @@
<maintainer type="project">
<email>wine@gentoo.org</email>
<name>Wine</name>
+ <description>
+ This package must be kept in sync with repo/proj/wine repository.
+ Any changes need to be run past the maintainer to ensure the two repositories are kept in sync.
+ </description>
</maintainer>
<maintainer type="person">
<email>commendsarnex@gmail.com</email>
next reply other threads:[~2018-01-22 22:51 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 22:51 NP Hardass [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-20 1:13 [gentoo-commits] repo/proj/wine:master commit in: app-emulation/wine-d3d9/ Sam James
2022-05-17 4:28 Sam James
2022-05-17 4:28 Sam James
2022-03-02 3:56 Sam James
2022-03-02 3:56 Sam James
2021-08-13 10:51 Jimi Huotari
2019-02-18 15:36 Nick Sarnie
2019-01-27 17:01 Nick Sarnie
2019-01-24 2:38 Nick Sarnie
2019-01-09 4:16 Nick Sarnie
2018-12-29 21:14 Nick Sarnie
2018-11-25 16:52 Nick Sarnie
2018-11-11 17:32 Nick Sarnie
2018-11-04 20:58 Nick Sarnie
2018-10-22 23:32 Nick Sarnie
2018-10-22 23:32 Nick Sarnie
2018-10-22 23:32 Nick Sarnie
2018-10-13 15:51 Nick Sarnie
2018-09-30 19:43 Nick Sarnie
2018-09-17 1:09 Nick Sarnie
2018-09-02 14:35 Nick Sarnie
2018-09-01 16:39 Nick Sarnie
2018-09-01 16:26 Nick Sarnie
2018-09-01 16:19 Nick Sarnie
2018-08-02 2:36 Nick Sarnie
2018-08-02 2:36 Nick Sarnie
2018-08-02 2:36 Nick Sarnie
2018-07-21 16:59 Nick Sarnie
2018-07-14 2:41 Nick Sarnie
2018-06-24 18:06 Nick Sarnie
2018-06-17 19:05 Nick Sarnie
2018-05-28 15:51 Nick Sarnie
2018-05-27 16:46 Nick Sarnie
2018-05-13 14:36 Nick Sarnie
2018-05-02 1:26 Nick Sarnie
2018-05-02 1:26 Nick Sarnie
2018-05-02 1:26 Nick Sarnie
2018-05-02 1:26 Nick Sarnie
2018-05-02 1:26 Nick Sarnie
2018-05-02 1:26 Nick Sarnie
2018-05-02 1:26 Nick Sarnie
2018-03-02 2:02 NP Hardass
2018-03-02 2:02 NP Hardass
2018-03-02 2:02 NP Hardass
2018-01-22 22:51 NP Hardass
2018-01-20 6:53 NP Hardass
2018-01-20 4:03 NP Hardass
2018-01-20 4:03 NP Hardass
2018-01-20 4:03 NP Hardass
2018-01-14 18:00 Jimi Huotari
2017-12-04 6:32 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=1516495827.12da1b95122afc023812e115118d1cef3e4a6949.np-hardass@gentoo \
--to=np-hardass@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