Github messages for voidlinux
 help / color / mirror / Atom feed
From: mhmdanas <mhmdanas@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Nim: update to v2.0.0, adopt
Date: Mon, 14 Aug 2023 14:23:27 +0200	[thread overview]
Message-ID: <20230814122327.ISY2tRuYtDX8j5IaqM78-q0xrMpXdcDn95SC0fqi8Mo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45597@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 855 bytes --]

New comment by mhmdanas on void-packages repository

https://github.com/void-linux/void-packages/pull/45597#issuecomment-1677220948

Comment:
@adigitoleo this seems to be your first contribution to void-packages, so the team will probably be hesitant to have you adopt the package right now, until you demonstrate a longer history of contributions. From https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#adopting-a-template:

> To ensure a template gets the care it needs, template adopters should be familiar with the package and have an established history of contributions to Void. Those who have contributed several updates, especially for the template in question, are good candidates for template maintainership.

Also, the package name is `nim`, not `Nim`, so please update your commit message and PR title accordingly.


  parent reply	other threads:[~2023-08-14 12:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14  3:59 [PR PATCH] " adigitoleo
2023-08-14  4:01 ` [PR PATCH] [Updated] " adigitoleo
2023-08-14  5:30 ` Bnyro
2023-08-14  5:30 ` Bnyro
2023-08-14  5:41 ` [PR PATCH] [Updated] " adigitoleo
2023-08-14  6:53 ` icp1994
2023-08-14  7:45 ` [PR PATCH] [Updated] " adigitoleo
2023-08-14 12:23 ` mhmdanas [this message]
2023-08-14 12:30 ` mhmdanas
2023-08-14 16:50 ` adigitoleo
2023-08-17 10:43 ` IcedQuinn
2023-08-20 11:51 ` adigitoleo
2023-08-20 11:51 ` [PR PATCH] [Closed]: " adigitoleo

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=20230814122327.ISY2tRuYtDX8j5IaqM78-q0xrMpXdcDn95SC0fqi8Mo@z \
    --to=mhmdanas@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).