From: benjcal <benjcal@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: msp430-toolchain: update to 9.3.1.2
Date: Mon, 19 Jun 2023 04:20:13 +0200 [thread overview]
Message-ID: <20230619022013.Fhxap92q4iX6580JnhKMrvHTPD1Huq8EQ39322xOrbM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44456@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 245 bytes --]
New comment by benjcal on void-packages repository
https://github.com/void-linux/void-packages/pull/44456#issuecomment-1596388291
Comment:
@classabbyamp does this looks good or do I still need to make a new PR? I don't see any merge conflicts
next prev parent reply other threads:[~2023-06-19 2:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 15:10 [PR PATCH] " benjcal
2023-06-15 15:11 ` [PR REVIEW] " benjcal
2023-06-15 15:12 ` benjcal
2023-06-15 15:19 ` benjcal
2023-06-15 15:21 ` benjcal
2023-06-15 15:22 ` [PR PATCH] [Updated] " benjcal
2023-06-17 20:12 ` benjcal
2023-06-17 20:12 ` benjcal
2023-06-18 18:31 ` benjcal
2023-06-18 20:41 ` benjcal
2023-06-19 2:20 ` benjcal [this message]
2023-07-26 13:59 ` [PR PATCH] [Closed]: " benjcal
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=20230619022013.Fhxap92q4iX6580JnhKMrvHTPD1Huq8EQ39322xOrbM@z \
--to=benjcal@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).