From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mdnsd/mDNSResponder: Conflicts with mDNSResponder/mdnsd
Date: Mon, 15 Nov 2021 15:55:48 +0100 [thread overview]
Message-ID: <20211115145548.-oxGBvx0wkXInX3dq-Z6KcFXVvs3lJEcTZ7CA9PLzOQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34090@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 259 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/pull/34090#issuecomment-968989981
Comment:
Only one of them needs the conflict, conflicts are mutual and making both conflict just results in two error messages.
next prev parent reply other threads:[~2021-11-15 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 7:27 [PR PATCH] " mikoxyz
2021-11-15 12:37 ` [PR PATCH] [Updated] " mikoxyz
2021-11-15 12:51 ` mikoxyz
2021-11-15 14:54 ` Duncaen
2021-11-15 14:55 ` Duncaen
2021-11-15 14:55 ` Duncaen [this message]
2021-11-15 15:16 ` [PR PATCH] [Updated] " mikoxyz
2021-11-15 15:16 ` mikoxyz
2021-11-16 12:17 ` [PR PATCH] [Merged]: mdnsd: Conflicts with mDNSResponder ericonr
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=20211115145548.-oxGBvx0wkXInX3dq-Z6KcFXVvs3lJEcTZ7CA9PLzOQ@z \
--to=duncaen@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).