From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Cyclic dependency: perl-HTML-Parser <-> perl-HTTP-Message
Date: Sat, 18 Sep 2021 21:07:00 +0200 [thread overview]
Message-ID: <20210918190700.MTfbv5wsxIlUgzI19J4bkc1zCOva3B8NUHJ9TIcIhlg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32468@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 438 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/issues/32468#issuecomment-922357937
Comment:
i think not testing is better because if tests are not cyclic, they can be properly automated (we could even have the builders run them eventually) while if you allow cycles they can't (and tests on stuff like this are mostly meaningless either way, i see no reason to let a few rare cases break it)
next prev parent reply other threads:[~2021-09-18 19:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 8:27 [ISSUE] " 4ricci
2021-08-12 15:13 ` ericonr
2021-08-12 15:40 ` Chocimier
2021-08-14 18:16 ` dkwo
2021-09-18 17:57 ` [ISSUE] [CLOSED] " 4ricci
2021-09-18 19:07 ` q66 [this message]
2021-09-18 19:07 ` q66
2021-09-19 10:11 ` dkwo
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=20210918190700.MTfbv5wsxIlUgzI19J4bkc1zCOva3B8NUHJ9TIcIhlg@z \
--to=q66@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).