From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: .github/workflows: disable scheduled cron jobs on forks
Date: Tue, 31 May 2022 05:27:52 +0200 [thread overview]
Message-ID: <20220531032752.RRcXDDS70jlkMrfTmEf1CzpqRxUu-ibiZcz-CucKQYc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37339@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 544 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/pull/37339#issuecomment-1141630967
Comment:
> Its also better to have a [seperate repository](https://github.com/Animeshz/void-xpackages) for personal packages
the way you do this will not work for anything that provides shlibs used by other packages, because of how `common/shlibs` and xbps(-src) shlib handling works.
fwiw I just keep packages that aren't submitted to the repos on other branches of my fork, rebasing them as needed.
next prev parent reply other threads:[~2022-05-31 3:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 4:28 [PR PATCH] " Animeshz
2022-05-30 20:22 ` dmarto
2022-05-30 20:47 ` dmarto
2022-05-31 3:19 ` Animeshz
2022-05-31 3:27 ` classabbyamp [this message]
2022-05-31 3:34 ` Animeshz
2022-05-31 4:00 ` 0x5c
2022-08-30 2:14 ` github-actions
2022-09-13 2:15 ` [PR PATCH] [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=20220531032752.RRcXDDS70jlkMrfTmEf1CzpqRxUu-ibiZcz-CucKQYc@z \
--to=classabbyamp@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).