From: CaitCatDev <CaitCatDev@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Update libdecor to 0.2.2 and gamescope to 3.14.23
Date: Fri, 19 Jul 2024 18:54:36 +0200 [thread overview]
Message-ID: <20240719165436.DDC4F22986@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-51338@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 726 bytes --]
New comment by CaitCatDev on void-packages repository
https://github.com/void-linux/void-packages/pull/51338#issuecomment-2239636006
Comment:
Apologies it seems githubs docs on updating a commit message close the request. I'll continue this in a new request.
> Please follow the [guidelines](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#committing-your-changes) for commit messages.
Hi sorry seems githubs docs on updating a commit message leads to the request being forced closed. But I have updated the commit messages to better reflect what has been updated and based them on what's in the CONTRIBUTING.MD file
New request here:
https://github.com/void-linux/void-packages/pull/51339
next prev parent reply other threads:[~2024-07-19 16:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 15:14 [PR PATCH] updated libdecor and gamescope CaitCatDev
2024-07-19 15:27 ` Update libdecor to 0.2.2 and gamescope to 3.14.23 CaitCatDev
2024-07-19 16:10 ` abenson
2024-07-19 16:40 ` [PR PATCH] [Closed]: " CaitCatDev
2024-07-19 16:54 ` CaitCatDev [this message]
2024-07-19 16:57 ` CaitCatDev
2024-07-19 17:52 ` dexgs
2024-07-19 16:53 [PR PATCH] Update Gamescope and libdecor CaitCatDev
2024-07-19 17:02 ` Update libdecor to 0.2.2 and gamescope to 3.14.23 abenson
2024-07-19 17:11 ` CaitCatDev
2024-07-19 17:17 ` CaitCatDev
2024-07-19 17:53 ` dexgs
2024-07-19 18:01 ` CaitCatDev
2024-07-19 18:02 ` CaitCatDev
2024-07-19 18:03 ` CaitCatDev
2024-07-19 18:14 ` dexgs
2024-07-19 18:24 ` CaitCatDev
2024-07-19 18:27 ` dexgs
2024-07-19 18:28 ` CaitCatDev
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=20240719165436.DDC4F22986@inbox.vuxu.org \
--to=caitcatdev@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).