Github messages for voidlinux
 help / color / mirror / Atom feed
From: OoLunar <OoLunar@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: dpp-10.0.23_1
Date: Sat, 04 Mar 2023 02:49:18 +0100	[thread overview]
Message-ID: <20230304014918.5LdtiBz1hdIQ5s2jx3a8qRRcKtfJ17YBNRbtdWINvks@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42521@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 442 bytes --]

New review comment by OoLunar on void-packages repository

https://github.com/void-linux/void-packages/pull/42521#discussion_r1125206752

Comment:
It's done here https://github.com/void-linux/void-packages/pull/38601/files#diff-1f1bf3035f39fc9c91e206b7219fd65d0544cdc55d7330fddf5f0e5b0d5e2419R25 though I don't know why. My guess was to remove previous files if the package was being reinstalled, hence "conflicts." It was incorrect phrasing

  parent reply	other threads:[~2023-03-04  1:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01  7:59 [PR PATCH] New package: libdpp-10.0.23_1 OoLunar
2023-03-02 21:50 ` [PR PATCH] [Updated] " OoLunar
2023-03-03  2:46 ` OoLunar
2023-03-03  3:30 ` OoLunar
2023-03-03 17:23 ` [PR REVIEW] New package: dpp-10.0.23_1 paper42
2023-03-03 17:26 ` OoLunar
2023-03-03 17:35 ` paper42
2023-03-04  1:48 ` OoLunar
2023-03-04  1:49 ` OoLunar [this message]
2023-03-04 22:20 ` paper42
2023-03-06  2:50 ` OoLunar
2023-03-06  2:52 ` [PR PATCH] [Updated] " OoLunar
2023-03-06  5:06 ` [PR REVIEW] " paper42
2023-03-06  5:17 ` [PR PATCH] [Updated] " OoLunar
2023-04-01 19:44 ` OoLunar
2023-06-27 11:55 ` [PR PATCH] [Closed]: " Duncaen

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=20230304014918.5LdtiBz1hdIQ5s2jx3a8qRRcKtfJ17YBNRbtdWINvks@z \
    --to=oolunar@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).