From: "Tomas Chvatal (scarabeus)" <scarabeus@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in eclass: subversion.eclass
Date: Wed, 29 Apr 2009 22:47:08 +0000 [thread overview]
Message-ID: <E1LzIYW-0008R6-4s@stork.gentoo.org> (raw)
scarabeus 09/04/29 22:47:08
Modified: subversion.eclass
Log:
Typo++. Well sometimes copy/pasto just does not work.
Revision Changes Path
1.66 eclass/subversion.eclass
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/subversion.eclass?rev=1.66&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/subversion.eclass?rev=1.66&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/subversion.eclass?r1=1.65&r2=1.66
Index: subversion.eclass
===================================================================
RCS file: /var/cvsroot/gentoo-x86/eclass/subversion.eclass,v
retrieving revision 1.65
retrieving revision 1.66
diff -u -r1.65 -r1.66
--- subversion.eclass 29 Apr 2009 22:26:31 -0000 1.65
+++ subversion.eclass 29 Apr 2009 22:47:08 -0000 1.66
@@ -1,6 +1,6 @@
# Copyright 1999-2009 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/eclass/subversion.eclass,v 1.65 2009/04/29 22:26:31 scarabeus Exp $
+# $Header: /var/cvsroot/gentoo-x86/eclass/subversion.eclass,v 1.66 2009/04/29 22:47:08 scarabeus Exp $
# @ECLASS: subversion.eclass
# @MAINTAINER:
@@ -375,7 +375,7 @@
# Default src_unpack. Fetch and, in older EAPIs, bootstrap.
subversion_src_unpack() {
subversion_fetch || die "${ESVN}: unknown problem occurred in subversion_fetch."
- has src_prepare ${EXPORTED_FUNCTIONS} || git_src_prepare
+ has src_prepare ${EXPORTED_FUNCTIONS} || subversion_src_prepare
}
# @FUNCTION: subversion_src_prepare
next reply other threads:[~2009-04-29 22:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 22:47 Tomas Chvatal (scarabeus) [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-07 1:59 [gentoo-commits] gentoo-x86 commit in eclass: subversion.eclass Mike Gilbert (floppym)
2012-02-14 16:08 Mike Frysinger (vapier)
2010-12-19 14:51 Justin Lecher (jlec)
2010-06-22 18:34 Arfrever Frehtes Taifersar Arahesis (arfrever)
2009-05-10 20:33 Arfrever Frehtes Taifersar Arahesis (arfrever)
2009-04-29 22:26 Tomas Chvatal (scarabeus)
2009-04-26 2:33 Arfrever Frehtes Taifersar Arahesis (arfrever)
2009-04-26 2:18 Arfrever Frehtes Taifersar Arahesis (arfrever)
2009-04-26 1:57 Arfrever Frehtes Taifersar Arahesis (arfrever)
2009-03-22 1:56 Arfrever Frehtes Taifersar Arahesis (arfrever)
2008-05-27 9:49 Bo Oersted Andresen (zlin)
2008-05-15 13:27 Bo Oersted Andresen (zlin)
2008-04-30 18:57 Benedikt Boehm (hollow)
2008-03-06 9:23 Bo Oersted Andresen (zlin)
2008-02-27 12:54 Bo Oersted Andresen (zlin)
2008-02-21 16:33 Bo Oersted Andresen (zlin)
2008-02-21 16:01 Bo Oersted Andresen (zlin)
2008-02-21 13:38 Bo Oersted Andresen (zlin)
2008-02-20 22:35 Bo Oersted Andresen (zlin)
2008-02-20 22:28 Bo Oersted Andresen (zlin)
2008-02-20 20:36 Bo Oersted Andresen (zlin)
2008-02-20 20:32 Bo Oersted Andresen (zlin)
2008-02-20 19:18 Doug Klima (cardoe)
2008-02-20 17:55 Doug Klima (cardoe)
2008-02-20 17:11 Bo Oersted Andresen (zlin)
2008-02-17 7:59 Akinori Hattori (hattya)
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=E1LzIYW-0008R6-4s@stork.gentoo.org \
--to=scarabeus@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