Github messages for voidlinux
 help / color / mirror / Atom feed
From: abenson <abenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: toot: update to 0.29.0
Date: Mon, 21 Nov 2022 20:20:40 +0100	[thread overview]
Message-ID: <20221121192040.9dinmsjUlBus702Fu6UDyVTvc_oC6ceBTPAaGk_TUEA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40583@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]

There's a merged pull request on the void-packages repository

toot: update to 0.29.0
https://github.com/void-linux/void-packages/pull/40583

Description:
Also change maintainer to me, since Nathan no longer uses Void.

<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**

Note, I'm using it as my main client, but have only tested the musl version. I did test cross-builds for `i686`, `armv6l` and `x86_64` though, without problem. And xlint gave no errors (trivial change).

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-MUSL)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - x86_64 (crossbuild)
  - armv6l (crossbuild)
  - i686 (crossbuild)


      parent reply	other threads:[~2022-11-21 19:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17 18:43 [PR PATCH] toot: upgrade to 0.28.1 j0ni
2022-11-17 18:45 ` [PR REVIEW] " abenson
2022-11-17 18:45 ` paper42
2022-11-17 18:45 ` abenson
2022-11-17 22:11 ` [PR PATCH] [Updated] " j0ni
2022-11-17 22:14 ` j0ni
2022-11-17 22:15 ` j0ni
2022-11-17 22:18 ` [PR REVIEW] " j0ni
2022-11-17 22:21 ` [PR PATCH] [Updated] " j0ni
2022-11-17 22:21 ` [PR REVIEW] " j0ni
2022-11-17 22:28 ` j0ni
2022-11-17 22:43 ` j0ni
2022-11-17 23:06 ` [PR REVIEW] " j0ni
2022-11-18 11:29 ` j0ni
2022-11-18 15:30 ` [PR PATCH] [Updated] " j0ni
2022-11-21 19:04 ` j0ni
2022-11-21 19:06 ` j0ni
2022-11-21 19:10 ` [PR REVIEW] toot: upgrade to 0.29.1 abenson
2022-11-21 19:10 ` abenson
2022-11-21 19:11 ` classabbyamp
2022-11-21 19:12 ` [PR PATCH] [Updated] " j0ni
2022-11-21 19:13 ` j0ni
2022-11-21 19:15 ` toot: update to 0.29.0 j0ni
2022-11-21 19:16 ` [PR PATCH] [Updated] " j0ni
2022-11-21 19:20 ` abenson [this message]

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=20221121192040.9dinmsjUlBus702Fu6UDyVTvc_oC6ceBTPAaGk_TUEA@z \
    --to=abenson@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).