From: jaminW55 <jaminW55@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: gazou-0.3.3
Date: Wed, 31 Jan 2024 04:37:26 +0100 [thread overview]
Message-ID: <20240131033726.103ED27FF4@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48160@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
New comment by jaminW55 on void-packages repository
https://github.com/void-linux/void-packages/pull/48160#issuecomment-1918322884
Comment:
> > In terms of moving this package forward into the repos, what else do we have left in the process?
>
> Merging of PRs can take some time. I believe that this PR is ready to be merged, some maintainer just has to take a look at it and merge it. Merging of new packages can take longer compared to simple package update PRs. See [CONTRIBUTING](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md)
Is it possible for me to takeover and move forward as maintainer? i think I have enough knowledge of this program and a bit more experience building void packages now that I could probably maintain it. It isn't updated too often and I'd like to get this moved to the repos.
Sorry for the delay, but any direction you could provide would be most appreciated.
next prev parent reply other threads:[~2024-01-31 3:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 22:19 [PR PATCH] " meator
2024-01-10 22:47 ` [PR PATCH] [Updated] " meator
2024-01-11 3:39 ` jaminW55
2024-01-11 3:43 ` jaminW55
2024-01-11 3:43 ` jaminW55
2024-01-11 3:44 ` jaminW55
2024-01-11 3:44 ` jaminW55
2024-01-11 3:44 ` jaminW55
2024-01-11 8:11 ` meator
2024-01-11 22:47 ` jaminW55
2024-01-12 7:03 ` meator
2024-01-12 17:13 ` jaminW55
2024-01-12 17:15 ` jaminW55
2024-01-12 20:20 ` meator
2024-01-17 7:55 ` jaminW55
2024-01-31 3:37 ` jaminW55 [this message]
2024-01-31 17:42 ` meator
2024-02-01 23:46 ` jaminW55
2024-02-01 23:47 ` jaminW55
2024-02-02 0:00 ` [PR REVIEW] " jaminW55
2024-02-02 0:00 ` jaminW55
2024-02-02 7:45 ` [PR PATCH] [Updated] " meator
2024-02-05 22:20 ` [PR REVIEW] " Piraty
2024-02-05 22:21 ` Piraty
2024-02-05 22:22 ` Piraty
2024-02-05 22:25 ` [PR PATCH] [Updated] " meator
2024-02-05 22:26 ` [PR REVIEW] " meator
2024-02-05 22:28 ` meator
2024-02-05 22:34 ` [PR PATCH] [Updated] " meator
2024-02-05 22:39 ` [PR REVIEW] " meator
2024-02-05 23:18 ` [PR PATCH] [Merged]: " Piraty
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=20240131033726.103ED27FF4@inbox.vuxu.org \
--to=jaminw55@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).