From: ipkalm <ipkalm@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: v2ray-4.39.2
Date: Fri, 25 Jun 2021 13:55:54 +0200 [thread overview]
Message-ID: <20210625115554.1GRS0gc1yK0FF9fSpjPf5C65-KHKzy6pZXBHBvF7bJM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30762@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 320 bytes --]
New comment by ipkalm on void-packages repository
https://github.com/void-linux/void-packages/pull/30762#issuecomment-868446501
Comment:
@abenson sorry, but I did many mistakes while work with fork (most big is create changes in master branch, not in separate branch). I promise to be more careful for the next time.
prev parent reply other threads:[~2021-06-25 11:55 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-09 12:38 [PR PATCH] New package: v2ray-4.38.3 ipkalm
2021-05-09 19:28 ` noarchwastaken
2021-05-09 19:28 ` noarchwastaken
2021-05-09 20:15 ` ericonr
2021-05-09 20:15 ` [PR REVIEW] " noarchwastaken
2021-05-09 20:15 ` noarchwastaken
2021-05-09 20:32 ` ericonr
2021-05-10 4:23 ` [PR PATCH] [Updated] " ipkalm
2021-05-10 4:24 ` ipkalm
2021-05-10 4:26 ` noarchwastaken
2021-05-10 4:32 ` ipkalm
2021-05-10 4:35 ` noarchwastaken
2021-05-10 4:35 ` noarchwastaken
2021-05-10 4:36 ` ipkalm
2021-05-10 9:18 ` [PR PATCH] [Updated] " ipkalm
2021-05-10 9:21 ` ipkalm
2021-05-10 9:40 ` [PR PATCH] [Updated] " ipkalm
2021-05-10 9:42 ` ipkalm
2021-05-10 10:02 ` ipkalm
2021-05-10 10:15 ` ipkalm
2021-05-10 10:19 ` ipkalm
2021-05-10 10:20 ` ipkalm
2021-05-10 14:28 ` noarchwastaken
2021-05-10 16:53 ` ipkalm
2021-05-10 20:25 ` noarchwastaken
2021-05-10 20:25 ` noarchwastaken
2021-05-10 20:39 ` ipkalm
2021-05-10 20:46 ` ipkalm
2021-05-11 17:14 ` ipkalm
2021-05-11 18:03 ` ericonr
2021-05-11 18:21 ` ipkalm
2021-05-11 18:21 ` ipkalm
2021-05-11 18:24 ` ipkalm
2021-05-11 18:24 ` ipkalm
2021-05-11 18:38 ` ericonr
2021-05-11 18:40 ` ipkalm
2021-05-12 18:06 ` [PR PATCH] [Updated] " ipkalm
2021-05-12 18:11 ` ipkalm
2021-05-12 19:06 ` [PR PATCH] [Closed]: " ipkalm
2021-05-12 19:06 ` [PR PATCH] [Updated] " ipkalm
2021-05-12 19:10 ` ipkalm
2021-05-12 19:15 ` ipkalm
2021-05-14 9:26 ` ipkalm
2021-05-14 9:26 ` ipkalm
2021-05-28 3:45 ` [PR PATCH] [Updated] " ipkalm
2021-06-24 4:19 ` [PR PATCH] [Updated] New package: v2ray-4.39.2 ipkalm
2021-06-24 4:22 ` ipkalm
2021-06-24 4:24 ` [PR PATCH] [Closed]: " ipkalm
2021-06-24 4:25 ` abenson
2021-06-25 11:55 ` ipkalm [this message]
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=20210625115554.1GRS0gc1yK0FF9fSpjPf5C65-KHKzy6pZXBHBvF7bJM@z \
--to=ipkalm@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).