From: "Yixun Lan" <dlan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-process/criu/
Date: Mon, 21 Mar 2016 06:15:06 +0000 (UTC) [thread overview]
Message-ID: <1458540876.7598248bcc81e500a1266b6990ad19d932d7c08f.dlan@gentoo> (raw)
commit: 7598248bcc81e500a1266b6990ad19d932d7c08f
Author: Yixun Lan <dlan <AT> gentoo <DOT> org>
AuthorDate: Mon Mar 21 06:14:36 2016 +0000
Commit: Yixun Lan <dlan <AT> gentoo <DOT> org>
CommitDate: Mon Mar 21 06:14:36 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7598248b
sys-process/criu: revision bump since libdir path changed
Package-Manager: portage-2.2.27
sys-process/criu/{criu-2.0.ebuild => criu-2.0-r1.ebuild} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
diff --git a/sys-process/criu/criu-2.0.ebuild b/sys-process/criu/criu-2.0-r1.ebuild
similarity index 100%
rename from sys-process/criu/criu-2.0.ebuild
rename to sys-process/criu/criu-2.0-r1.ebuild
next reply other threads:[~2016-03-21 6:15 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 6:15 Yixun Lan [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-22 8:55 [gentoo-commits] repo/gentoo:master commit in: sys-process/criu/ WANG Xuerui
2024-08-22 8:55 WANG Xuerui
2024-04-29 10:36 Joonas Niilola
2024-01-21 15:15 Florian Schmaus
2024-01-21 14:52 Florian Schmaus
2024-01-21 9:44 Florian Schmaus
2023-07-08 3:39 Sam James
2023-07-07 4:40 Sam James
2023-07-07 3:36 Sam James
2023-05-01 12:52 Sam James
2023-02-25 12:48 Joonas Niilola
2022-11-15 18:22 Michał Górny
2022-11-03 6:15 Sam James
2022-11-03 6:15 Sam James
2022-11-02 23:14 Sam James
2022-07-03 23:54 Sam James
2022-06-07 8:24 Jakov Smolić
2022-06-07 6:34 Joonas Niilola
2022-06-03 8:12 Sam James
2022-06-03 6:58 Sam James
2022-03-25 9:46 Jakov Smolić
2022-03-25 4:23 Sam James
2022-02-02 20:52 Arthur Zamarin
2022-02-02 8:02 Agostino Sarubbo
2021-09-03 1:53 Sam James
2021-07-20 0:51 Georgy Yakovlev
2021-06-01 6:32 Agostino Sarubbo
2020-11-25 3:45 Patrick McLean
2020-09-25 8:45 Agostino Sarubbo
2020-09-24 8:29 Georgy Yakovlev
2020-09-24 1:53 Georgy Yakovlev
2020-09-22 20:25 Georgy Yakovlev
2020-09-22 20:25 Georgy Yakovlev
2020-08-02 17:37 Patrick McLean
2020-05-15 17:36 Patrick McLean
2019-12-29 9:56 David Seifert
2019-10-20 6:29 Yixun Lan
2019-07-28 19:39 Matthias Maier
2019-07-28 19:39 Matthias Maier
2019-03-02 9:57 Sergei Trofimovich
2019-01-12 23:29 Sergei Trofimovich
2019-01-12 23:29 Sergei Trofimovich
2018-05-07 6:38 Mike Frysinger
2018-04-30 15:58 Mike Gilbert
2018-02-22 9:05 Agostino Sarubbo
2018-02-12 3:05 Matthias Maier
2018-02-12 3:05 Matthias Maier
2018-01-22 1:42 Zac Medico
2017-12-16 0:24 Matthias Maier
2017-11-12 21:08 Justin Lecher
2017-09-21 21:06 Mike Gilbert
2017-05-26 22:54 David Seifert
2017-03-30 6:32 Yixun Lan
2017-03-10 7:49 Yixun Lan
2017-03-10 7:49 Yixun Lan
2017-02-22 9:08 Yixun Lan
2017-02-15 21:45 Yixun Lan
2017-01-19 1:47 Yixun Lan
2016-12-20 19:21 Tobias Klausmann
2016-10-18 20:49 Yixun Lan
2016-10-18 20:49 Yixun Lan
2016-09-20 6:35 Yixun Lan
2016-09-20 6:35 Yixun Lan
2016-07-04 19:05 Stephen Klimaszewski
2016-05-27 9:33 Lars Wendler
2016-03-15 15:13 Alexis Ballier
2016-03-15 15:13 Alexis Ballier
2015-08-19 6:53 Yixun Lan
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=1458540876.7598248bcc81e500a1266b6990ad19d932d7c08f.dlan@gentoo \
--to=dlan@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