Github messages for voidlinux
 help / color / mirror / Atom feed
From: the-maldridge <the-maldridge@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: lurch / libomemo: 12-byte IVs patch
Date: Thu, 14 Jan 2021 02:52:29 +0100	[thread overview]
Message-ID: <20210114015229.0jO786a4DJNB1H8J5B6aoTEFu2MbG2g27JZ0v1nGgrk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26757@inbox.vuxu.org>

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

New comment by the-maldridge on void-packages repository

https://github.com/void-linux/void-packages/issues/26757#issuecomment-759872002

Comment:
Great, if you look at the timeline you'll see the revert happened before 0.7.0 was cut.  Again, Void's patch policy is not to accept patches from random people on the internet trying to bypass upstream review protocols, and so your patch was reverted.  You are welcome to submit a patch to update the package to the now released version which would be the appropriate way to get the update into Void.  Do note that as this is now OT for this issue and the content of this issue is now resolved, I'm unsubscribed from further notifications.

      parent reply	other threads:[~2021-01-14  1:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26757@inbox.vuxu.org>
2020-11-30  4:25 ` eli-schwartz
2020-11-30  4:31 ` ericonr
2020-11-30  7:32 ` Neustradamus
2020-11-30 12:26 ` ericonr
2020-11-30 12:30 ` leahneukirchen
2020-11-30 12:42 ` ericonr
2020-11-30 14:11 ` Neustradamus
2020-11-30 14:22 ` q66
2020-11-30 14:30 ` leahneukirchen
2020-11-30 14:36 ` ericonr
2020-11-30 14:49 ` Neustradamus
2021-01-14  1:29 ` Neustradamus
2021-01-14  1:44 ` the-maldridge
2021-01-14  1:46 ` Neustradamus
2021-01-14  1:51 ` Neustradamus
2021-01-14  1:52 ` the-maldridge [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=20210114015229.0jO786a4DJNB1H8J5B6aoTEFu2MbG2g27JZ0v1nGgrk@z \
    --to=the-maldridge@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).