From: "Mike Frysinger (vapier)" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in eclass: multilib.eclass
Date: Thu, 10 Mar 2011 05:01:47 +0000 (UTC) [thread overview]
Message-ID: <20110310050147.7C82420054@flycatcher.gentoo.org> (raw)
vapier 11/03/10 05:01:47
Modified: multilib.eclass
Log:
fix typo in new multilib_env export code pointed out by Ryan
Revision Changes Path
1.84 eclass/multilib.eclass
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/eclass/multilib.eclass?rev=1.84&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/eclass/multilib.eclass?rev=1.84&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/eclass/multilib.eclass?r1=1.83&r2=1.84
Index: multilib.eclass
===================================================================
RCS file: /var/cvsroot/gentoo-x86/eclass/multilib.eclass,v
retrieving revision 1.83
retrieving revision 1.84
diff -u -r1.83 -r1.84
--- multilib.eclass 10 Mar 2011 04:29:58 -0000 1.83
+++ multilib.eclass 10 Mar 2011 05:01:47 -0000 1.84
@@ -1,6 +1,6 @@
# Copyright 1999-2008 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/eclass/multilib.eclass,v 1.83 2011/03/10 04:29:58 vapier Exp $
+# $Header: /var/cvsroot/gentoo-x86/eclass/multilib.eclass,v 1.84 2011/03/10 05:01:47 vapier Exp $
# @ECLASS: multilib.eclass
# @MAINTAINER:
@@ -674,7 +674,7 @@
;;
esac
- export MULTILIB_ABIS MULTILIB_ABI
+ export MULTILIB_ABIS DEFAULT_ABI
}
# @FUNCTION: multilib_toolchain_setup
next reply other threads:[~2011-03-10 5:01 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 5:01 Mike Frysinger (vapier) [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-17 7:44 [gentoo-commits] gentoo-x86 commit in eclass: multilib.eclass Mike Frysinger (vapier)
2014-01-17 6:21 Mike Frysinger (vapier)
2013-04-22 1:18 Mike Frysinger (vapier)
2012-10-17 19:13 Mike Frysinger (vapier)
2012-08-27 15:04 Mike Frysinger (vapier)
2012-08-22 16:03 Mike Frysinger (vapier)
2012-06-03 8:27 Mike Frysinger (vapier)
2011-12-10 19:41 Mike Frysinger (vapier)
2011-10-27 5:50 Mike Frysinger (vapier)
2011-10-17 19:14 Mike Frysinger (vapier)
2011-10-14 22:54 Mike Frysinger (vapier)
2011-03-18 22:03 Mike Frysinger (vapier)
2011-03-18 21:58 Mike Frysinger (vapier)
2011-03-18 21:56 Mike Frysinger (vapier)
2011-03-18 19:13 Mike Frysinger (vapier)
2011-03-18 19:12 Mike Frysinger (vapier)
2011-03-16 20:09 Mike Frysinger (vapier)
2011-03-10 4:29 Mike Frysinger (vapier)
2011-03-10 4:26 Mike Frysinger (vapier)
2011-03-10 1:52 Mike Frysinger (vapier)
2011-03-07 2:46 Mike Frysinger (vapier)
2010-08-14 21:31 Harald van Dijk (truedfx)
2009-10-08 20:10 Fabian Groffen (grobian)
2009-10-08 19:56 Fabian Groffen (grobian)
2009-10-08 19:54 Fabian Groffen (grobian)
2009-06-14 11:40 Fabian Groffen (grobian)
2009-04-04 18:02 Fabian Groffen (grobian)
2009-02-20 23:20 Mike Frysinger (vapier)
2009-02-09 19:53 Markus Meier (maekke)
2009-01-09 6:59 Mike Frysinger (vapier)
2008-11-28 9:20 Mike Frysinger (vapier)
2008-11-28 6:31 Mike Frysinger (vapier)
2008-06-01 1:38 Mike Frysinger (vapier)
2008-06-01 1:37 Mike Frysinger (vapier)
2008-05-02 4:07 Mike Frysinger (vapier)
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=20110310050147.7C82420054@flycatcher.gentoo.org \
--to=vapier@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