Github messages for voidlinux
 help / color / mirror / Atom feed
From: steinex <steinex@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] git-team: update to 1.7.1.
Date: Sun, 09 Oct 2022 20:31:48 +0200	[thread overview]
Message-ID: <20221009183148.3jkmBg3x2Y3EZkl2gl7ogGo1w3f_Bx9fa-v-x98VvWQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39843@inbox.vuxu.org>

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

There is an updated pull request by steinex against master on the void-packages repository

https://github.com/steinex/void-packages git-team
https://github.com/void-linux/void-packages/pull/39843

git-team: update to 1.7.1.
<!-- Uncomment relevant sections and delete options which are not applicable -->

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

<!--
#### 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-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


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

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

From 3ad202d4ae7419b1e2e283ccfbcff53d4c14e854 Mon Sep 17 00:00:00 2001
From: Frank Steinborn <steinex@nognu.de>
Date: Sun, 9 Oct 2022 20:05:12 +0200
Subject: [PATCH] git-team: update to 1.7.1.

---
 srcpkgs/git-team/template | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/git-team/template b/srcpkgs/git-team/template
index 6501dfe4c212..357773afe940 100644
--- a/srcpkgs/git-team/template
+++ b/srcpkgs/git-team/template
@@ -1,6 +1,6 @@
 # Template file for 'git-team'
 pkgname=git-team
-version=1.7.0
+version=1.7.1
 revision=1
 build_style=go
 go_import_path=github.com/hekmekk/git-team
@@ -8,8 +8,9 @@ short_desc="Manage and enhance git commit messages with co-authors"
 maintainer="Frank Steinborn <steinex@nognu.de>"
 license="MIT"
 homepage="https://github.com/hekmekk/git-team"
+changelog="https://raw.githubusercontent.com/hekmekk/git-team/main/CHANGELOG.md"
 distfiles="${homepage}/archive/v${version}.tar.gz"
-checksum=c52d800ea3b5f45896d4f21ab4944d1f45dd8d90cdf1a634a445d22b93a31f49
+checksum=d16fa6ea10afd3d9fff0b63321d2c347a170acffa4d8e9bf0f8de0e7ef24b85b
 
 post_install() {
 	vlicense LICENSE

  reply	other threads:[~2022-10-09 18:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-09 18:26 [PR PATCH] " steinex
2022-10-09 18:31 ` steinex [this message]
2022-10-11  4:28 ` [PR PATCH] [Merged]: " classabbyamp

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=20221009183148.3jkmBg3x2Y3EZkl2gl7ogGo1w3f_Bx9fa-v-x98VvWQ@z \
    --to=steinex@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).