public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ben Kohler" <bkohler@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/memtest86+/
Date: Wed, 29 Jun 2022 15:42:23 +0000 (UTC)	[thread overview]
Message-ID: <1656517335.9848a4c79182a5c4c3738c5559fcc36c0b55a08d.bkohler@gentoo> (raw)

commit:     9848a4c79182a5c4c3738c5559fcc36c0b55a08d
Author:     Ben Kohler <bkohler <AT> gentoo <DOT> org>
AuthorDate: Wed Jun 29 15:09:55 2022 +0000
Commit:     Ben Kohler <bkohler <AT> gentoo <DOT> org>
CommitDate: Wed Jun 29 15:42:15 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9848a4c7

sys-apps/memtest86+: fix minor use-conditional typo

Closes: https://bugs.gentoo.org/855143

Signed-off-by: Ben Kohler <bkohler <AT> gentoo.org>

 sys-apps/memtest86+/memtest86+-6.00_beta2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-apps/memtest86+/memtest86+-6.00_beta2.ebuild b/sys-apps/memtest86+/memtest86+-6.00_beta2.ebuild
index 2107fd4d4b8f..add994f6a7ec 100644
--- a/sys-apps/memtest86+/memtest86+-6.00_beta2.ebuild
+++ b/sys-apps/memtest86+/memtest86+-6.00_beta2.ebuild
@@ -44,7 +44,7 @@ src_compile() {
 	pushd build64
 		use bios64 && emake memtest.bin
 		use efi64 && emake memtest.efi
-		use iso32 && emake iso
+		use iso64 && emake iso
 	popd
 }
 


             reply	other threads:[~2022-06-29 15:42 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 15:42 Ben Kohler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-14 19:01 [gentoo-commits] repo/gentoo:master commit in: sys-apps/memtest86+/ Ben Kohler
2024-03-29 15:18 Ben Kohler
2024-01-14 21:00 Ben Kohler
2024-01-07 17:19 Andrew Ammerlaan
2023-12-28 14:16 Ben Kohler
2023-11-03 12:23 Ben Kohler
2023-08-17  7:49 Andrew Ammerlaan
2023-07-14 13:00 Ben Kohler
2023-05-19 13:17 Ben Kohler
2023-05-19 13:05 Ben Kohler
2023-05-10 18:02 Ben Kohler
2023-03-31 12:57 Ben Kohler
2023-03-30 16:42 Sam James
2023-03-30 16:12 Arthur Zamarin
2023-02-05 13:35 Ben Kohler
2023-02-03 13:02 Ben Kohler
2022-12-30 15:59 Ben Kohler
2022-11-30  0:52 Sam James
2022-11-30  0:52 Sam James
2022-11-12 15:36 Ben Kohler
2022-10-25 18:05 Sam James
2022-10-25 13:00 Ben Kohler
2022-08-16 15:15 Ben Kohler
2022-07-18 13:47 Ben Kohler
2022-07-02 12:01 Ben Kohler
2022-07-01 15:36 Ben Kohler
2022-06-14 16:05 Ben Kohler
2022-01-18 12:24 Sam James
2022-01-18 12:24 Sam James
2022-01-04 16:13 Ben Kohler
2021-12-03 16:17 Ben Kohler
2021-12-03 16:17 Ben Kohler
2021-10-03 11:28 David Seifert
2021-09-16 14:56 Ben Kohler
2021-09-16 14:56 Ben Kohler
2021-08-13 13:22 Lars Wendler
2021-05-26  8:33 David Seifert
2021-05-23 23:05 Agostino Sarubbo
2021-05-23 22:28 Agostino Sarubbo
2021-04-21 19:02 Sam James
2019-11-13 19:58 Aaron Bauman
2019-09-01  7:43 Mikle Kolyada
2018-08-08 21:56 Mikle Kolyada
2018-08-06 22:20 Thomas Deutschmann
2018-06-19 19:54 Richard Farina
2018-06-03  2:59 Aaron Bauman
2017-03-17 10:26 Agostino Sarubbo
2017-03-17 10:15 Agostino Sarubbo
2017-03-15  7:45 Mike Frysinger
2017-03-14 23:37 Mike Frysinger
2017-02-09 15:29 Mike Frysinger
2015-12-12 23:24 Mike Frysinger

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=1656517335.9848a4c79182a5c4c3738c5559fcc36c0b55a08d.bkohler@gentoo \
    --to=bkohler@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