Github messages for voidlinux
 help / color / mirror / Atom feed
From: ivmai <ivmai@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libatomic_ops: update to 7.6.14
Date: Sun, 28 Aug 2022 10:50:46 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38952@inbox.vuxu.org> (raw)

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

There is a new pull request by ivmai against master on the void-packages repository

https://github.com/ivmai/void-linux-packages patch-3
https://github.com/void-linux/void-packages/pull/38952

libatomic_ops: update to 7.6.14
Also, maintainer is specified.

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

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

<!--
#### 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 (x64)


A patch file from https://github.com/void-linux/void-packages/pull/38952.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-3-38952.patch --]
[-- Type: text/x-diff, Size: 1256 bytes --]

From 175b8d3f2d84429e23c32270fb9420920d6e6427 Mon Sep 17 00:00:00 2001
From: Ivan Maidanski <ivmai@mail.ru>
Date: Sun, 28 Aug 2022 11:47:16 +0300
Subject: [PATCH] libatomic_ops: update to 7.6.14

Also, maintainer is specified.
---
 srcpkgs/libatomic_ops/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/libatomic_ops/template b/srcpkgs/libatomic_ops/template
index 9fce059f86f3..478b76349b3e 100644
--- a/srcpkgs/libatomic_ops/template
+++ b/srcpkgs/libatomic_ops/template
@@ -1,15 +1,15 @@
 # Template file for 'libatomic_ops'
 pkgname=libatomic_ops
-version=7.6.12
+version=7.6.14
 revision=1
 build_style=gnu-configure
 configure_args="--enable-shared --enable-static"
 short_desc="Semi-portable access to hardware provided atomic memory operations"
-maintainer="Orphaned <orphan@voidlinux.org>"
+maintainer="Ivan Maidanski <ivmai@mail.ru>"
 license="GPL-2.0-or-later, MIT"
 homepage="https://github.com/ivmai/libatomic_ops"
 distfiles="${homepage}/releases/download/v${version}/libatomic_ops-${version}.tar.gz"
-checksum=f0ab566e25fce08b560e1feab6a3db01db4a38e5bc687804334ef3920c549f3e
+checksum=390f244d424714735b7050d056567615b3b8f29008a663c262fb548f1802d292
 
 post_install() {
 	vlicense doc/LICENSING.txt

             reply	other threads:[~2022-08-28  8:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-28  8:50 ivmai [this message]
2022-08-30 21:05 ` ivmai
2022-08-31 20:47 ` ivmai
2022-08-31 20:58 ` [PR PATCH] [Merged]: " leahneukirchen
2022-08-31 21:27 ` ivmai

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38952@inbox.vuxu.org \
    --to=ivmai@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).