From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] python3-babelfish: update to 0.6.0.
Date: Sat, 16 Oct 2021 21:52:48 +0200 [thread overview]
Message-ID: <20211016195248.GdIB90fsFB5v_YZsZuXuZxcMRBRWuuqnAozaFTuw6dY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33590@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 244 bytes --]
New review comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/33590#discussion_r730306151
Comment:
From CI:
```
srcpkgs/python3-babelfish/template:4: revision should be set to 1 on update
```
next prev parent reply other threads:[~2021-10-16 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 19:17 [PR PATCH] " dm1tz
2021-10-16 19:52 ` ericonr [this message]
2021-10-16 20:49 ` [PR PATCH] [Updated] " dm1tz
2021-10-16 21:02 ` [PR REVIEW] " dm1tz
2021-10-18 13:14 ` [PR PATCH] [Updated] " dm1tz
2021-10-18 13:18 ` [PR PATCH] [Closed]: " dm1tz
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=20211016195248.GdIB90fsFB5v_YZsZuXuZxcMRBRWuuqnAozaFTuw6dY@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).