From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: atuin-12.0.0
Date: Sat, 19 Nov 2022 21:50:19 +0100 [thread overview]
Message-ID: <20221119205019.8TYBy4it3fM71JZQkj1JkwLB0LvXiwet7B3LZp-uHxE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40600@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 264 bytes --]
New review comment by tranzystorek-io on void-packages repository
https://github.com/void-linux/void-packages/pull/40600#discussion_r1027141498
Comment:
Yeah, so my understanding is, as long as the package builds and runs, we could merge this for now as-is, no?
next prev parent reply other threads:[~2022-11-19 20:50 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 23:53 [PR PATCH] " tranzystorek-io
2022-11-19 11:31 ` [PR REVIEW] " jcgruenhage
2022-11-19 11:33 ` jcgruenhage
2022-11-19 11:37 ` tranzystorek-io
2022-11-19 14:06 ` jcgruenhage
2022-11-19 14:09 ` tranzystorek-io
2022-11-19 16:30 ` jcgruenhage
2022-11-19 20:50 ` tranzystorek-io [this message]
2022-11-19 22:01 ` [PR PATCH] [Updated] " tranzystorek-io
2022-12-21 10:33 ` tranzystorek-io
2023-02-26 21:43 ` tranzystorek-io
2023-03-05 13:10 ` [PR REVIEW] " jcgruenhage
2023-04-02 8:16 ` [PR PATCH] [Updated] " tranzystorek-io
2023-04-02 8:42 ` [PR PATCH] [Updated] New package: atuin-14.0.0 tranzystorek-io
2023-04-16 16:16 ` tranzystorek-io
2023-04-16 16:38 ` [PR REVIEW] New package: atuin-14.0.1 jcgruenhage
2023-05-14 11:08 ` [PR PATCH] [Updated] " tranzystorek-io
2023-05-28 22:33 ` tranzystorek-io
2023-06-09 22:03 ` [PR PATCH] [Updated] New package: atuin-15.0.0 tranzystorek-io
2023-06-09 22:38 ` tranzystorek-io
2023-06-11 19:10 ` tranzystorek-io
2023-08-07 10:55 ` tranzystorek-io
2023-10-26 8:02 ` [PR PATCH] [Updated] New package: atuin-16.0.0 tranzystorek-io
2023-10-29 9:08 ` [PR PATCH] [Updated] New package: atuin-17.0.0 tranzystorekk
2023-11-26 9:31 ` [PR PATCH] [Updated] New package: atuin-17.0.1 tranzystorekk
2023-11-26 13:37 ` [PR REVIEW] " icp1994
2023-11-27 8:13 ` tranzystorekk
2023-11-27 9:53 ` icp1994
2023-11-27 20:19 ` [PR PATCH] [Updated] " tranzystorekk
2023-11-27 20:32 ` classabbyamp
2023-12-10 13:58 ` tranzystorekk
2023-12-12 11:59 ` New package: atuin-17.1.0 tranzystorekk
2023-12-12 12:52 ` icp1994
2023-12-12 15:17 ` [PR PATCH] [Updated] " tranzystorekk
2023-12-13 9:54 ` tranzystorekk
2023-12-13 9:57 ` tranzystorekk
2023-12-13 17:00 ` [PR PATCH] [Merged]: " classabbyamp
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=20221119205019.8TYBy4it3fM71JZQkj1JkwLB0LvXiwet7B3LZp-uHxE@z \
--to=tranzystorek-io@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).