From: zimoun <zimon.toutoune@gmail.com>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: 34613@debbugs.gnu.org
Subject: [bug#34613] [PATCH] gnu: Add prometheus.
Date: Sat, 08 Oct 2022 16:42:44 +0200 [thread overview]
Message-ID: <86pmf2s7ff.fsf_-_@gmail.com> (raw)
In-Reply-To: <86mtgx2i0r.fsf@gmail.com> (zimoun's message of "Thu, 07 Apr 2022 14:29:56 +0200")
On Thu, 07 Apr 2022 at 14:29, zimoun <zimon.toutoune@gmail.com> wrote:
> What is the status of this old patch#34613:
>
> <http://issues.guix.gnu.org/issue/34613>
> Because the Go ecosystem changed a bit since the submission, do we merge
> this patch? Especially in the light of:
>
> There are some problems with it however:
>
> The tarball has a vendor directory, containing sources of third party
> go stuff. How do we deal with that?
> (Should we package the stuff there, and link the sources into the tree?)
>
>
> <https://issues.guix.gnu.org/issue/34613#1>
>
> Well, I propose to drop this submission since the last interaction is
> from 3 years, 2 weeks, 6 days ago and then start a fresh one. WDYT?
The patch is marked moreinfo since 23 Jun 2022 (15 weeks, 2 days, 6
hours ago) and dormant since years.
If no objection, I will close it soon.
Cheers,
simon
next prev parent reply other threads:[~2022-10-08 15:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 11:45 [bug#34613] [PATCH] gnu: Add prometheus Gábor Boskovits
[not found] ` <handler.34613.B.155083599830524.ack@debbugs.gnu.org>
2019-02-22 12:21 ` [bug#34613] Acknowledgement ([PATCH] gnu: Add prometheus.) Gábor Boskovits
2019-03-11 22:19 ` Ludovic Courtès
2019-03-12 7:03 ` Pierre Neidhardt
2019-03-12 19:31 ` Leo Famulari
2019-03-12 21:24 ` Gábor Boskovits
2019-03-12 21:29 ` Gábor Boskovits
2019-03-13 10:06 ` Ludovic Courtès
2019-03-13 12:33 ` Gábor Boskovits
2019-03-18 8:31 ` Ludovic Courtès
2022-04-07 12:29 ` [bug#34613] [PATCH] gnu: Add prometheus zimoun
2022-10-08 14:42 ` zimoun [this message]
2022-10-18 16:18 ` bug#34613: " zimoun
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=86pmf2s7ff.fsf_-_@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=34613@debbugs.gnu.org \
--cc=boskovits@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.