public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pyprof2calltree/
Date: Fri,  5 Jan 2018 23:19:37 +0000 (UTC)	[thread overview]
Message-ID: <1515194363.de4f4d8777fd16a67c4da4157c9dfa5f2822df18.mgorny@gentoo> (raw)

commit:     de4f4d8777fd16a67c4da4157c9dfa5f2822df18
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Fri Jan  5 22:17:17 2018 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Fri Jan  5 23:19:23 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=de4f4d87

dev-python/pyprof2calltree: Clean old up

 dev-python/pyprof2calltree/Manifest                    |  1 -
 .../pyprof2calltree/pyprof2calltree-1.3.2.ebuild       | 18 ------------------
 2 files changed, 19 deletions(-)

diff --git a/dev-python/pyprof2calltree/Manifest b/dev-python/pyprof2calltree/Manifest
index e873ece3838..ddf94826fa4 100644
--- a/dev-python/pyprof2calltree/Manifest
+++ b/dev-python/pyprof2calltree/Manifest
@@ -1,2 +1 @@
-DIST pyprof2calltree-1.3.2.tar.gz 6609 BLAKE2B 302f9d11250aaeefef278f6ad176f39d97676ae4a62175af2b279b97898419a5083c4cc9de36b9b65896b43853f71c342583f8d2d002be177ecb1b68e49df998 SHA512 e85c5a21fe52b246ee6080f59e2ff115b43e3ab634e2842aff0d493b8b996105e0c1698e049ae7d11ea53c1f1fd601ef5f12c6fba62dcea28ddff23ec61a2736
 DIST pyprof2calltree-1.4.0.tar.gz 7784 BLAKE2B e8b9ecd857930406bb3b7f7851913a68f1e3433f3b42c262922b5d5b0fbfa692078fdad811d4ca358f7c74d14320c914cfa779ed0b9da8c4fcd7d8e021fd3319 SHA512 b1acba29cd4e5112012eeeffdac53900688a28707306ef3a8a3827f7422c35bc921d59d33db3209db923bb8640014e7d9d7d819eafbcb19e0cf7e6159537bded

diff --git a/dev-python/pyprof2calltree/pyprof2calltree-1.3.2.ebuild b/dev-python/pyprof2calltree/pyprof2calltree-1.3.2.ebuild
deleted file mode 100644
index 477d26d8b8a..00000000000
--- a/dev-python/pyprof2calltree/pyprof2calltree-1.3.2.ebuild
+++ /dev/null
@@ -1,18 +0,0 @@
-# Copyright 1999-2015 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=5
-PYTHON_COMPAT=( python{2_7,3_4} )
-
-inherit distutils-r1
-
-DESCRIPTION="convert python profile data to kcachegrind calltree form"
-HOMEPAGE="https://pypi.python.org/pypi/pyprof2calltree/"
-SRC_URI="mirror://pypi/p/${PN}/${PF}.tar.gz"
-IUSE=
-
-LICENSE="MIT"
-SLOT="0"
-KEYWORDS="~amd64 ~x86"
-
-DEPEND="dev-python/setuptools[${PYTHON_USEDEP}]"


             reply	other threads:[~2018-01-05 23:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05 23:19 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-02-11  5:11 [gentoo-commits] repo/gentoo:master commit in: dev-python/pyprof2calltree/ Sam James
2021-02-11  5:11 Sam James
2021-02-11  5:11 Sam James
2021-05-07 11:11 Michał Górny
2021-05-07 11:11 Michał Górny
2022-05-28 18:35 Arthur Zamarin
2022-05-28 18:35 Arthur Zamarin
2022-06-16  8:08 Michał Górny
2023-10-20 14:05 Michał Górny
2023-11-23 18:55 Michał Górny
2024-10-08  6:24 Sam James
2024-10-08  6:26 Sam James
2024-10-08  6:26 Sam James
2024-10-08  6:26 Sam James

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=1515194363.de4f4d8777fd16a67c4da4157c9dfa5f2822df18.mgorny@gentoo \
    --to=mgorny@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