From: "Matt Thode" <prometheanfire@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/cryptography-vectors/
Date: Wed, 1 Aug 2018 18:37:49 +0000 (UTC) [thread overview]
Message-ID: <1533148651.0cc4fe4edaedd5ed4d9875e4b6f73700f1c55f88.prometheanfire@gentoo> (raw)
commit: 0cc4fe4edaedd5ed4d9875e4b6f73700f1c55f88
Author: Matthew Thode <prometheanfire <AT> gentoo <DOT> org>
AuthorDate: Wed Aug 1 18:37:05 2018 +0000
Commit: Matt Thode <prometheanfire <AT> gentoo <DOT> org>
CommitDate: Wed Aug 1 18:37:31 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0cc4fe4e
dev-python/cryptography-vectors: cleaing up manifest
Package-Manager: Portage-2.3.43, Repoman-2.3.10
dev-python/cryptography-vectors/Manifest | 3 ---
1 file changed, 3 deletions(-)
diff --git a/dev-python/cryptography-vectors/Manifest b/dev-python/cryptography-vectors/Manifest
index a77d313827d..b290b4fc468 100644
--- a/dev-python/cryptography-vectors/Manifest
+++ b/dev-python/cryptography-vectors/Manifest
@@ -1,5 +1,2 @@
-DIST cryptography_vectors-1.7.1.tar.gz 26652514 BLAKE2B 5aa670b4d52b010964465091660205fea4b7de1099701e25a6e31da9a7ea4a312a81a488ed369ac6b032e8232514361f87f1b0946cb55e0e0a18955874d2f09b SHA512 2edaa91198adcf5e2523ea8d3d25a8cd7df85e6f6c06618301f87af6f0133f5d4672721082205a9a3c0c648390ee772e6107eb6ba76e96649bc2832676df8283
-DIST cryptography_vectors-2.0.2.tar.gz 27011827 BLAKE2B eda02ca72a4a6a608050c531fc649a9843a9b7083a0a7a726ac89201f37016e258538671b15d4197deaffdb6902c345ff40e1da604e2b6034148d9c204b0ab1d SHA512 ab14bdf664e6df08c8436eb24c4465d3080aacd4e6cb47a0113b0877f869cd91d4184ad9122a428b323e91316b686eeb167c4e932773cac1e7b2adbc9309ca36
-DIST cryptography_vectors-2.1.4.tar.gz 27255711 BLAKE2B 6c842b6366d794e9986110479e2175996b344aa191345c85a5cec8c0640b7a67b157f310eca31ac8e6487739357b11a2b86b9832fc680318e754c4751414c754 SHA512 74c2c1e3924f848488a3b5abdabda1a0089ae7d070b94e65f9fa2bf2da057ad27a37e46f90de4f2c3e9f1cc96c1c179cb5dbf0f50d5166a02846923e3bceb165
DIST cryptography_vectors-2.2.2.tar.gz 27270814 BLAKE2B b57cfd402e85e34a1e52d034ef51699ba9ab7381e5baa28f0f062ecc8d6b7b5849ac4d5426c41768e1a4fb9462f84d7e22476ec64dc0bd0142a799caaf95eafb SHA512 bdaf53c8087d6c44fcd3ab54069d1d45b60ee80d98fd813fe180b9e88272203b5dd2abd5fa6dcd3b4ce9ec3215997fd8e99e63309e2f0ac619a6f72d552afff9
DIST cryptography_vectors-2.3.tar.gz 35303908 BLAKE2B 694f5a741ddedce2101632dcf165961d4706feaa5c8482235f5afb69f4257bfb4f8a9b8423213661de0da2d56ebf43cc7ba138a4bbf9462f367ebd5adf2620f7 SHA512 7c51b0c29c182c4da3265824a1b6e44c943bd41dfa89199cded963d0182a8ade678a560ec9ea13f6e8918119fcacf1c90d804cc90368e51cc5d430228448231c
next reply other threads:[~2018-08-01 18:37 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 18:37 Matt Thode [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-17 14:23 [gentoo-commits] repo/gentoo:master commit in: dev-python/cryptography-vectors/ Michał Górny
2019-11-17 14:11 Michał Górny
2019-11-17 14:05 Michał Górny
2019-11-16 13:53 Michał Górny
2019-09-01 20:47 Matthew Thode
2019-05-11 19:06 Matthew Thode
2019-02-17 18:39 Matthew Thode
2018-12-14 8:06 Patrick McLean
2018-11-10 0:46 Patrick McLean
2018-07-29 16:47 Patrick Lauer
2018-07-29 6:07 Patrick Lauer
2018-02-21 20:18 Michał Górny
2018-01-23 20:18 Michał Górny
2018-01-03 9:11 Michał Górny
2017-12-09 1:23 Tim Harder
2017-11-09 8:28 Patrick Lauer
2017-10-29 6:18 Tim Harder
2017-10-22 13:45 Patrick Lauer
2017-09-30 1:03 Matt Thode
2017-08-16 12:40 Michał Górny
2017-07-31 16:47 Michał Górny
2017-06-09 11:53 Dirkjan Ochtman
2017-05-03 11:02 Michał Górny
2017-04-25 19:50 Dirkjan Ochtman
2017-02-28 21:39 Michael Weber
2017-02-25 7:39 Markus Meier
2017-02-06 3:31 Lars Wendler
2017-02-06 3:31 Lars Wendler
2017-01-24 11:46 Agostino Sarubbo
2017-01-23 6:11 Jeroen Roovers
2017-01-22 20:25 Tobias Klausmann
2017-01-21 17:27 Agostino Sarubbo
2017-01-21 17:16 Agostino Sarubbo
2016-12-21 15:30 Lars Wendler
2016-11-26 23:05 Lars Wendler
2016-11-13 8:52 Markus Meier
2016-11-09 13:55 Lars Wendler
2016-11-09 13:55 Lars Wendler
2016-11-06 21:39 Matt Thode
2016-10-01 21:12 Patrick Lauer
2016-10-01 13:48 Jeroen Roovers
2016-09-22 8:30 Tobias Klausmann
2016-09-10 20:03 Dirkjan Ochtman
2016-07-22 13:28 Bernard Cafarelli
2016-06-21 2:47 Mike Frysinger
2016-06-06 16:15 Agostino Sarubbo
2016-06-04 6:28 Dirkjan Ochtman
2016-06-04 6:28 Dirkjan Ochtman
2016-06-02 18:24 Markus Meier
2016-06-01 12:55 Tobias Klausmann
2016-04-03 18:30 Patrick Lauer
2016-03-22 10:55 Agostino Sarubbo
2016-03-20 10:19 Dirkjan Ochtman
2016-03-20 10:19 Dirkjan Ochtman
2016-03-02 6:11 Mike Frysinger
2016-02-20 14:24 Markus Meier
2016-02-17 5:53 Jeroen Roovers
2016-02-13 15:33 Agostino Sarubbo
2016-02-09 16:43 Tobias Klausmann
2016-02-01 11:13 Justin Lecher
2016-01-10 8:23 Justin Lecher
2015-12-11 15:32 Justin Lecher
2015-11-20 11:29 Justin Lecher
2015-11-20 11:29 Justin Lecher
2015-11-07 23:32 Mikle Kolyada
2015-11-05 10:58 Agostino Sarubbo
2015-11-04 14:48 Agostino Sarubbo
2015-10-29 10:44 Justin Lecher
2015-10-17 11:03 Markus Meier
2015-09-30 3:36 Jeroen Roovers
2015-09-29 12:33 Agostino Sarubbo
2015-09-29 12:32 Agostino Sarubbo
2015-09-28 15:27 Tobias Klausmann
2015-09-28 7:58 Justin Lecher
2015-09-06 18:00 Justin Lecher
2015-08-24 14:04 Agostino Sarubbo
2015-08-24 14:02 Agostino Sarubbo
2015-08-13 10:23 Justin Lecher
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=1533148651.0cc4fe4edaedd5ed4d9875e4b6f73700f1c55f88.prometheanfire@gentoo \
--to=prometheanfire@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