Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: rsyslog: update to 8.2110.0.
Date: Sun, 14 Nov 2021 08:04:09 +0100	[thread overview]
Message-ID: <20211114070409.uqthsRaEb6-ghqMaJen9UoVzS2IGYNCXW9EPH9LAuik@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31718@inbox.vuxu.org>

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

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

rsyslog: update to 8.2110.0.
https://github.com/void-linux/void-packages/pull/31718

Description:
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (x86_64-glibc)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->


      parent reply	other threads:[~2021-11-14  7:04 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30  0:10 [PR PATCH] rsyslog: update to 8.2106.0 baal-zebub
2021-06-30 12:54 ` baal-zebub
2021-06-30 14:39 ` zdykstra
2021-06-30 17:26 ` baal-zebub
2021-06-30 17:28 ` baal-zebub
2021-06-30 19:15 ` zdykstra
2021-06-30 19:41 ` [PR PATCH] [Updated] " baal-zebub
2021-06-30 19:50 ` baal-zebub
2021-06-30 19:54 ` baal-zebub
2021-06-30 20:53 ` zdykstra
2021-06-30 22:26 ` baal-zebub
2021-06-30 22:36 ` zdykstra
2021-06-30 22:58 ` baal-zebub
2021-07-02 18:36 ` zdykstra
2021-07-03  3:25 ` ericonr
2021-07-04 19:03 ` [PR PATCH] [Updated] " baal-zebub
2021-07-04 20:09 ` baal-zebub
2021-07-04 21:33 ` baal-zebub
2021-07-31 14:48 ` baal-zebub
2021-07-31 14:49 ` baal-zebub
2021-07-31 14:50 ` baal-zebub
2021-08-03  4:02 ` ericonr
2021-08-04 20:47 ` baal-zebub
2021-08-04 20:47 ` baal-zebub
2021-08-04 20:48 ` baal-zebub
2021-11-04 19:18 ` [PR PATCH] [Updated] " baal-zebub
2021-11-06 11:54 ` [PR PATCH] [Updated] rsyslog: update to 8.2110.0 baal-zebub
2021-11-14  7:04 ` ericonr
2021-11-14  7:04 ` ericonr [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=20211114070409.uqthsRaEb6-ghqMaJen9UoVzS2IGYNCXW9EPH9LAuik@z \
    --to=ericonr@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).