public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michael Haubenwallner" <haubi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-portage/prefix-toolkit/
Date: Tue, 26 Mar 2019 16:11:32 +0000 (UTC)	[thread overview]
Message-ID: <1553616665.c5d81d96d4c2686650764240950f0d4cbe11d1b5.haubi@gentoo> (raw)

commit:     c5d81d96d4c2686650764240950f0d4cbe11d1b5
Author:     Michael Haubenwallner <haubi <AT> gentoo <DOT> org>
AuthorDate: Tue Mar 26 16:09:45 2019 +0000
Commit:     Michael Haubenwallner <haubi <AT> gentoo <DOT> org>
CommitDate: Tue Mar 26 16:11:05 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c5d81d96

app-portage/prefix-toolkit: restore ~x86-winnt keyword

As x86-winnt is stacked prefix only, no portage does have that keyword,
so it was accidentally dropped in last commit.

Package-Manager: Portage-2.3.51, Repoman-2.3.11
Signed-off-by: Michael Haubenwallner <haubi <AT> gentoo.org>

 app-portage/prefix-toolkit/prefix-toolkit-0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-portage/prefix-toolkit/prefix-toolkit-0.ebuild b/app-portage/prefix-toolkit/prefix-toolkit-0.ebuild
index ec2ac9f17b8..ae2ca111bab 100644
--- a/app-portage/prefix-toolkit/prefix-toolkit-0.ebuild
+++ b/app-portage/prefix-toolkit/prefix-toolkit-0.ebuild
@@ -11,7 +11,7 @@ LICENSE="GPL-3"
 SLOT="0"
 
 [[ ${PV} == 9999 ]] ||
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sparc ~x86 ~ppc-aix ~x64-cygwin ~amd64-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~m68k-mint ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sparc ~x86 ~ppc-aix ~x64-cygwin ~amd64-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~m68k-mint ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris ~x86-winnt"
 
 DEPEND=""
 RDEPEND="


             reply	other threads:[~2019-03-26 16:11 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-26 16:11 Michael Haubenwallner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-27 10:44 [gentoo-commits] repo/gentoo:master commit in: app-portage/prefix-toolkit/ Fabian Groffen
2023-05-27 10:15 Fabian Groffen
2023-05-27  9:29 Sam James
2023-05-26  6:25 Sam James
2023-05-26  6:23 Sam James
2023-05-26  6:23 Sam James
2023-05-26  6:23 Sam James
2023-04-24 20:15 Sam James
2023-04-24 20:15 Sam James
2023-04-24 20:13 Sam James
2022-07-11 20:19 Jakov Smolić
2021-06-02 19:01 Sam James
2021-01-06 13:23 Fabian Groffen
2020-12-27 14:01 Fabian Groffen
2020-03-13 14:35 Michael Haubenwallner
2020-03-13 14:35 Michael Haubenwallner
2020-03-09 14:56 Michael Haubenwallner
2020-03-09 14:56 Michael Haubenwallner
2020-03-09 14:56 Michael Haubenwallner
2019-09-05 10:30 Michael Haubenwallner
2019-09-04 10:31 Michael Haubenwallner
2019-09-04 10:31 Michael Haubenwallner
2019-06-25  9:21 Michael Haubenwallner
2019-06-17  9:44 Michael Haubenwallner
2019-06-12 15:32 Michael Haubenwallner
2019-06-05 15:39 Michael Haubenwallner
2019-05-21  8:48 Michael Haubenwallner
2019-03-26 15:58 Michael Haubenwallner
2019-03-25 14:19 Michael Haubenwallner

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=1553616665.c5d81d96d4c2686650764240950f0d4cbe11d1b5.haubi@gentoo \
    --to=haubi@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