From: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>
To: Sharlatan Hellseher <sharlatanus@gmail.com>
Cc: 69512@debbugs.gnu.org
Subject: [bug#69512] [PATCH] gnu: Add go-github-com-hashicorp-go-multierror.
Date: Sun, 03 Mar 2024 22:18:12 +0300 [thread overview]
Message-ID: <87ttlnf7kb.fsf@gmail.com> (raw)
In-Reply-To: <CAO+9K5qD1gS7HVfpB1mJ1tgs0z9Gx8+LAs2rQpSNVGG=o5viWg@mail.gmail.com> (Sharlatan Hellseher's message of "Sun, 3 Mar 2024 17:51:13 +0000")
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
Hi!
> Thank you for the patches!
Thank you for the patch review. ;-)
> There is a conflict to apply these patches, may you check please?
Okay, I re-based my patchset onto the "master" branch; no conflicts
were found in the process.
> I would suggest to place go-github-com-hashicorp-go-multierror
> in golang-check, It seams to me more suitable module.
I see that the "golang-check" module is for testing-related Go packages,
but it seems to me that "go-multierror" has wider range of use cases
than mere testing purposes (judging by its description at least.)
Could you elaborate?
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-03 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 20:31 [bug#69512] [PATCH] gnu: Add go-github-com-hashicorp-go-multierror Artyom V. Poptsov
2024-03-03 17:51 ` Sharlatan Hellseher
2024-03-03 19:18 ` Artyom V. Poptsov [this message]
2024-03-05 10:14 ` Sharlatan Hellseher
2024-03-05 19:47 ` Artyom V. Poptsov
2024-03-07 0:03 ` bug#69512: " 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=87ttlnf7kb.fsf@gmail.com \
--to=poptsov.artyom@gmail.com \
--cc=69512@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 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.