From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Manual.md: No mention of replaces
Date: Fri, 05 Feb 2021 03:42:02 +0100 [thread overview]
Message-ID: <20210205024202.W0u4p-gDo22-qNfDDF_BxhBzfNZs6SP7xETkyj6Hjlk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22424@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 253 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/22424#issuecomment-773744176
Comment:
Now that this mechanism is being used in removed-packages, it should definitely be documented.
@Chocimier ?
next prev parent reply other threads:[~2021-02-05 2:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 8:28 [ISSUE] (Manual.md) " toluschr
2020-05-31 2:07 ` Manual.md: " sgn
2020-11-07 8:36 ` ashpooljh
2021-02-05 2:42 ` ericonr [this message]
2021-03-11 19:45 ` Chocimier
2021-03-11 19:53 ` ericonr
2021-03-11 19:53 ` ericonr
2021-03-11 20:11 ` ashpooljh
2022-04-16 2:02 ` github-actions
2022-04-30 2:13 ` [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=20210205024202.W0u4p-gDo22-qNfDDF_BxhBzfNZs6SP7xETkyj6Hjlk@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).