From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: File conflict between cmark and python3-commonmark
Date: Wed, 15 Dec 2021 03:59:00 +0100 [thread overview]
Message-ID: <20211215025900.v3-urlN10Gw16azBYLm3tMmKgolRLkdFfu1RCwezjhw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34007@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 297 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/34007#issuecomment-994244383
Comment:
I think we usually spell out "python3-" in these executable names, but if other distros uses py3 it might help to go with the flow. I will check them out.
next prev parent reply other threads:[~2021-12-15 2:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 11:20 [ISSUE] " travankor
2021-11-11 1:50 ` ericonr
2021-11-11 1:51 ` ericonr
2021-12-15 2:01 ` bobertlo
2021-12-15 2:59 ` ericonr [this message]
2021-12-15 2:59 ` ericonr
2021-12-15 3:04 ` bobertlo
2022-07-06 2:13 ` github-actions
2022-07-21 2:14 ` [ISSUE] [CLOSED] " github-actions
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=20211215025900.v3-urlN10Gw16azBYLm3tMmKgolRLkdFfu1RCwezjhw@z \
--to=ericonr@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).