From: "Alexandre Restovtsev" <tetromino@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gnome:gnome-next commit in: eclass/
Date: Sun, 25 Sep 2011 20:33:51 +0000 (UTC) [thread overview]
Message-ID: <1b4f01e680929bdf55e2258e5f2f823171219a51.tetromino@gentoo> (raw)
commit: 1b4f01e680929bdf55e2258e5f2f823171219a51
Author: Alexandre Rostovtsev <tetromino <AT> gmail <DOT> com>
AuthorDate: Sun Sep 25 20:31:19 2011 +0000
Commit: Alexandre Restovtsev <tetromino <AT> gmail <DOT> com>
CommitDate: Sun Sep 25 20:31:19 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/gnome.git;a=commit;h=1b4f01e6
eclass/gnome2-live.eclass: switch to git-2.eclass
Now that bug #383761 has been fixed, we can switch to git-2 without
forcing live users to reclone all their repositories. Acked by Nirbheek
on IRC.
---
eclass/gnome2-live.eclass | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/eclass/gnome2-live.eclass b/eclass/gnome2-live.eclass
index 638cdc9..3a4dd6a 100644
--- a/eclass/gnome2-live.eclass
+++ b/eclass/gnome2-live.eclass
@@ -12,7 +12,7 @@
#
-inherit autotools gnome2 gnome2-utils libtool git
+inherit autotools gnome2 gnome2-utils libtool git-2
# Stolen from git.eclass
EXPORTED_FUNCTIONS="src_unpack pkg_postinst"
@@ -58,7 +58,7 @@ gnome2-live_src_unpack() {
if test -n "${A}"; then
unpack ${A}
fi
- git_src_unpack
+ git-2_src_unpack
has src_prepare ${EXPORTED_FUNCTIONS} || gnome2-live_src_prepare
}
next reply other threads:[~2011-09-25 20:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-25 20:33 Alexandre Restovtsev [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-01 22:51 [gentoo-commits] proj/gnome:gnome-next commit in: eclass/ Gilles Dartiguelongue
2011-09-27 13:36 Nirbheek Chauhan
2011-09-26 4:46 Alexandre Restovtsev
2011-09-20 2:16 Alexandre Restovtsev
2011-09-19 23:22 Alexandre Restovtsev
2011-08-28 18:46 Alexandre Restovtsev
2011-08-24 16:32 Alexandre Restovtsev
2011-08-21 7:10 Alexandre Restovtsev
2011-07-19 0:22 Alexandre Restovtsev
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=1b4f01e680929bdf55e2258e5f2f823171219a51.tetromino@gentoo \
--to=tetromino@gmail.com \
--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