From: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>
To: Sharlatan Hellseher <sharlatanus@gmail.com>
Cc: 69842@debbugs.gnu.org
Subject: [bug#69842] [PATCH] gnu: Add go-github-com-multiformats-go-varint.
Date: Sun, 17 Mar 2024 17:36:56 +0300 [thread overview]
Message-ID: <87r0g8sz5j.fsf@gmail.com> (raw)
In-Reply-To: <CAO+9K5qwK8mCVfojjDQvCpub7FMz2R6h4t=8m4uskP8MQQsyLQ@mail.gmail.com> (Sharlatan Hellseher's message of "Sun, 17 Mar 2024 13:42:15 +0000")
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
Hello!
> Please avoid adding new packages into golang.scm, It is in a
> proces of redistribution among submodules.
I know that you're working on splitting Go packages between more
specific modules.
I placed the new package into "golang.scm" only because other
"go-github-com-multiformats-*" packages are placed here.
Maybe it's reasonable to move all "go-github-com-multiformats-*" to
"golang-xyz.scm" first and then place the new packages from this group
here. What do you think?
Could you merge "go-github-com-multiformats-go-varint" after the review
process (and maybe with corrections to the package from my side) and
then move all "go-github-com-multiformats-*" to "golang-xyz.scm"?
Thanks!
- avp
--
Artyom "avp" Poptsov <poptsov.artyom@gmail.com>
Home page: https://memory-heap.org/~avp/
CADR Hackerspace co-founder: https://cadrspace.ru/
GPG: D0C2 EAC1 3310 822D 98DE B57C E9C5 A2D9 0898 A02F
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 869 bytes --]
next prev parent reply other threads:[~2024-03-17 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 12:10 [bug#69842] [PATCH] gnu: Add go-github-com-multiformats-go-varint Artyom V. Poptsov
2024-03-17 13:42 ` Sharlatan Hellseher
2024-03-17 14:36 ` Artyom V. Poptsov [this message]
2024-03-17 16:23 ` Sharlatan Hellseher
2024-03-21 23:57 ` bug#69842: " 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0g8sz5j.fsf@gmail.com \
--to=poptsov.artyom@gmail.com \
--cc=69842@debbugs.gnu.org \
--cc=sharlatanus@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).