From: Sharlatan Hellseher <sharlatanus@gmail.com>
To: 67263@debbugs.gnu.org
Subject: [bug#67263] [PATCH 0/8] adding nats-server package
Date: Thu, 1 Feb 2024 19:55:45 +0000 [thread overview]
Message-ID: <CAO+9K5oQty2xo_KBzfV1jLZ-M__W8cWAjoK0tj3e8otbfm1vjQ@mail.gmail.com> (raw)
In-Reply-To: <cover.1700330009.git.benjamin@uvy.fr>
[-- Attachment #1: Type: text/plain, Size: 452 bytes --]
Hi,
Thank you for the patches!
I started the review process for this series.
NATS is in the same group as nsq, rabitmq, Kafka.
see <https://gcore.com/learning/nats-rabbitmq-nsq-kafka-comparison/>.
We may place it to high-availability module next to nsq.
golang.scm is a process of split into logical modules (golang-check,
golang-crypto, golang-web, gokang-xyz). I would place
packages which provides golag modules in any relevant.
Thanks,
Oleg
[-- Attachment #2: Type: text/html, Size: 877 bytes --]
next prev parent reply other threads:[~2024-02-01 20:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 18:14 [bug#67263] [PATCH 0/8] adding nats-server package Benjamin
2023-11-18 18:17 ` [bug#67263] [PATCH 1/8] gnu: Add go-github-com-minio-highwayhash Benjamin
2023-11-18 18:17 ` [bug#67263] [PATCH 2/8] gnu: Add go-github-com-prashantv-gostub Benjamin
2023-11-18 18:17 ` [bug#67263] [PATCH 3/8] gnu: Add go-go-uber-org-automaxprocs Benjamin
2023-11-18 18:17 ` [bug#67263] [PATCH 4/8] gnu: Add go-github-com-nats-io-nuid Benjamin
2023-11-18 18:17 ` [bug#67263] [PATCH 5/8] gnu: Add go-github-com-nats-io-nkeys Benjamin
2023-11-18 18:17 ` [bug#67263] [PATCH 6/8] gnu: Add go-github-com-nats-io-jwt-v2 Benjamin
2023-11-18 18:17 ` [bug#67263] [PATCH 7/8] gnu: Add go-github-com-nats-io-nats-go Benjamin
2023-11-18 18:17 ` [bug#67263] [PATCH 8/8] gnu: Add nats-server Benjamin
2024-02-01 19:55 ` Sharlatan Hellseher [this message]
2024-02-08 21:55 ` bug#67263: [PATCH 0/8] adding nats-server package Sharlatan Hellseher
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=CAO+9K5oQty2xo_KBzfV1jLZ-M__W8cWAjoK0tj3e8otbfm1vjQ@mail.gmail.com \
--to=sharlatanus@gmail.com \
--cc=67263@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.