From: sirkhancision <sirkhancision@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: omegat-4.3.3
Date: Tue, 15 Nov 2022 05:18:31 +0100 [thread overview]
Message-ID: <20221115041831.uA6dHypbzHk1SBZUT-u37R6Ju6ico_42f_gOIRv-2RM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40500@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 416 bytes --]
New review comment by sirkhancision on void-packages repository
https://github.com/void-linux/void-packages/pull/40500#discussion_r1022300547
Comment:
Instead of using vcopy to copy the entire directory, I'm now using vdoc on the actual documentation files that come specifically with the local build. Should fix it, indeed.
That is, of course, if the vcopy on the other directories don't create a new problem :p
next prev parent reply other threads:[~2022-11-15 4:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 8:06 [PR PATCH] " sirkhancision
2022-11-13 8:14 ` [PR REVIEW] " classabbyamp
2022-11-13 8:14 ` classabbyamp
2022-11-13 8:14 ` classabbyamp
2022-11-13 8:14 ` classabbyamp
2022-11-13 8:14 ` classabbyamp
2022-11-13 8:14 ` classabbyamp
2022-11-13 8:14 ` classabbyamp
2022-11-13 8:14 ` classabbyamp
2022-11-13 8:14 ` classabbyamp
2022-11-13 19:51 ` [PR PATCH] [Updated] " sirkhancision
2022-11-13 19:55 ` sirkhancision
2022-11-14 4:40 ` [PR PATCH] [Updated] " sirkhancision
2022-11-14 4:43 ` sirkhancision
2022-11-14 22:18 ` [PR REVIEW] " classabbyamp
2022-11-14 22:18 ` classabbyamp
2022-11-14 22:18 ` classabbyamp
2022-11-15 0:52 ` sirkhancision
2022-11-15 0:53 ` classabbyamp
2022-11-15 4:14 ` [PR PATCH] [Updated] " sirkhancision
2022-11-15 4:15 ` [PR REVIEW] " sirkhancision
2022-11-15 4:17 ` sirkhancision
2022-11-15 4:18 ` sirkhancision [this message]
2022-11-15 17:58 ` sirkhancision
2022-12-04 4:14 ` [PR PATCH] [Updated] " sirkhancision
2022-12-04 4:16 ` sirkhancision
2022-12-06 19:45 ` sirkhancision
2023-03-07 2:07 ` github-actions
2023-03-22 1:54 ` [PR PATCH] [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=20221115041831.uA6dHypbzHk1SBZUT-u37R6Ju6ico_42f_gOIRv-2RM@z \
--to=sirkhancision@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).