From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: lolcat-c: update to 1.4 version.
Date: Tue, 28 Feb 2023 22:58:15 +0100 [thread overview]
Message-ID: <20230228215815.hB0LeK949au1TOlwFxwHqVG06Sr853y5UoVjPk_WzWg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42482@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 391 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/42482#issuecomment-1448978995
Comment:
> This seems to be on the git cli, i don’t have access to it rn… is there a way to do it with github directly?
The github interface is incredibly limited and not usable for any serious work, it's probably not possible without regular git CLI.
next prev parent reply other threads:[~2023-02-28 21:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 11:50 [PR PATCH] Update lolcat-c " SpidFightFR
2023-02-27 18:56 ` icp1994
2023-02-28 5:12 ` lolcat-c: update " SpidFightFR
2023-02-28 5:16 ` icp1994
2023-02-28 5:53 ` SpidFightFR
2023-02-28 21:58 ` paper42 [this message]
2023-03-01 10:22 ` SpidFightFR
2023-03-01 10:42 ` paper42
2023-03-01 12:04 ` SpidFightFR
2023-03-01 12:45 ` paper42
2023-03-01 12:45 ` paper42
2023-03-01 12:45 ` paper42
2023-03-01 12:59 ` SpidFightFR
2023-03-01 13:22 ` [PR PATCH] [Updated] " SpidFightFR
2023-03-01 13:25 ` SpidFightFR
2023-03-01 13:43 ` paper42
2023-03-01 14:35 ` SpidFightFR
2023-03-01 14:36 ` SpidFightFR
2023-03-01 16:15 ` paper42
2023-03-01 18:35 ` [PR PATCH] [Updated] " SpidFightFR
2023-03-01 18:36 ` SpidFightFR
2023-03-01 18:55 ` paper42
2023-03-01 18:58 ` lolcat-c: update to 1.4 SpidFightFR
2023-03-01 19:06 ` paper42
2023-03-01 19:07 ` SpidFightFR
2023-03-01 19:11 ` [PR PATCH] [Updated] " SpidFightFR
2023-03-01 19:12 ` SpidFightFR
2023-03-02 21:14 ` paper42
2023-03-02 21:14 ` [PR PATCH] [Merged]: " paper42
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=20230228215815.hB0LeK949au1TOlwFxwHqVG06Sr853y5UoVjPk_WzWg@z \
--to=paper42@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).