From: mjyut <mjyut@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] Move package requests elsewhere
Date: Sun, 17 Apr 2022 12:00:49 +0200 [thread overview]
Message-ID: <20220417100049.zW9ANTyV62hlt-_78kIuWiYJ68GJTYvWY9ONP8RR8dc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36700@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
New comment by mjyut on void-packages repository
https://github.com/void-linux/void-packages/issues/36700#issuecomment-1100844632
Comment:
I don't understand why someone said
> requests shouldn't be taken via github issues
so it's just an idea.
Create a new GItHub repository for only package request issues (e.g. `void-linux/void-package-request`) .
Perhaps the only content in that new repository is the `README.md`.
Then [transfer](https://docs.github.com/en/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository) the existing request issues to the new repository.
Pros:
* The existing request will be saved as is.
* If someone accidentally creates an isuue in the original package repository, it can be easily transferred by the contributors.
next prev parent reply other threads:[~2022-04-17 10:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 3:22 [ISSUE] " 0x5c
2022-04-17 10:00 ` mjyut [this message]
2022-04-17 16:34 ` mjyut
2022-04-17 16:46 ` Duncaen
2022-04-17 16:47 ` Duncaen
2022-04-17 16:47 ` Duncaen
2022-04-17 16:50 ` Duncaen
2022-04-17 17:02 ` mjyut
2022-04-17 17:26 ` mjyut
2022-04-20 0:25 ` 0x5c
2022-04-20 11:27 ` prez
2022-04-21 20:34 ` 0x5c
2022-04-21 20:36 ` Duncaen
2022-07-21 2:15 ` github-actions
2022-08-07 2:14 ` [ISSUE] [CLOSED] " github-actions
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=20220417100049.zW9ANTyV62hlt-_78kIuWiYJ68GJTYvWY9ONP8RR8dc@z \
--to=mjyut@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).