From: fccapria <fccapria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: element-desktop: Updated launch script with electron24
Date: Mon, 15 May 2023 20:48:52 +0200 [thread overview]
Message-ID: <20230515184852.RozubVntx26XgfR9dR2rxm7RaIgjhVWN1nI-OiY-6Xw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43885@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 228 bytes --]
New comment by fccapria on void-packages repository
https://github.com/void-linux/void-packages/pull/43885#issuecomment-1548380247
Comment:
> can you make the commit message more descriptive (like the PR title)?
Of course.
next prev parent reply other threads:[~2023-05-15 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 18:44 [PR PATCH] " fccapria
2023-05-15 18:47 ` classabbyamp
2023-05-15 18:48 ` fccapria [this message]
2023-05-15 19:45 ` fccapria
2023-05-15 19:51 ` fccapria
2023-05-15 19:52 ` classabbyamp
2023-05-16 10:57 ` fccapria
2023-05-16 10:59 ` [PR PATCH] [Merged]: " Johnnynator
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=20230515184852.RozubVntx26XgfR9dR2rxm7RaIgjhVWN1nI-OiY-6Xw@z \
--to=fccapria@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).