From: "Brian Dolbec" <dolsen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:repoman commit in: pym/portage/
Date: Tue, 27 Jun 2017 20:06:06 +0000 (UTC) [thread overview]
Message-ID: <1497546330.ff2c1d017cf2f8aa6a8eba4e0495089c5d73f277.dolsen@gentoo> (raw)
commit: ff2c1d017cf2f8aa6a8eba4e0495089c5d73f277
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Thu Jun 15 07:25:23 2017 +0000
Commit: Brian Dolbec <dolsen <AT> gentoo <DOT> org>
CommitDate: Thu Jun 15 17:05:30 2017 +0000
URL: https://gitweb.gentoo.org/proj/portage.git/commit/?id=ff2c1d01
const: Remove unused MANIFEST1_REQUIRED_HASH
The MANIFEST1_REQUIRED_HASH constant is not used anywhere, so it should
be possible to remove it safely.
Reviewed-by: Zac Medico <zmedico <AT> gentoo.org>
pym/portage/const.py | 1 -
1 file changed, 1 deletion(-)
diff --git a/pym/portage/const.py b/pym/portage/const.py
index 7e415ba9c..052d4ca2f 100644
--- a/pym/portage/const.py
+++ b/pym/portage/const.py
@@ -206,7 +206,6 @@ EAPI = 6
HASHING_BLOCKSIZE = 32768
MANIFEST1_HASH_FUNCTIONS = ("MD5", "SHA256", "RMD160")
-MANIFEST1_REQUIRED_HASH = "MD5"
# Past events:
#
next reply other threads:[~2017-06-27 20:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 20:06 Brian Dolbec [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-30 5:20 [gentoo-commits] proj/portage:repoman commit in: pym/portage/ Zac Medico
2018-03-30 0:48 Brian Dolbec
2018-03-29 21:35 Brian Dolbec
2017-12-06 0:16 Brian Dolbec
2017-12-05 18:32 Brian Dolbec
2017-11-26 17:46 Brian Dolbec
2017-09-11 21:43 Brian Dolbec
2017-08-17 1:59 Brian Dolbec
2017-07-10 22:31 Brian Dolbec
2017-07-10 17:52 Brian Dolbec
2017-06-27 20:06 Brian Dolbec
2016-04-30 0:12 [gentoo-commits] proj/portage:master " Brian Dolbec
2016-05-03 6:11 ` [gentoo-commits] proj/portage:repoman " Brian Dolbec
2016-04-29 23:16 [gentoo-commits] proj/portage:master " Brian Dolbec
2016-05-03 6:11 ` [gentoo-commits] proj/portage:repoman " Brian Dolbec
2015-12-30 23:38 Brian Dolbec
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=1497546330.ff2c1d017cf2f8aa6a8eba4e0495089c5d73f277.dolsen@gentoo \
--to=dolsen@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