From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] git-cliff: generate and ship man page
Date: Sun, 18 Sep 2022 17:45:27 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39344@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]
There is a new pull request by jcgruenhage against master on the void-packages repository
https://github.com/jcgruenhage/void-packages git-cliff-0.9.0_2
https://github.com/void-linux/void-packages/pull/39344
git-cliff: generate and ship man page
<!-- Uncomment relevant sections and delete options which are not applicable -->
Motivation here is that running `git cliff --help` doesn't give any reasonable
output (just complains that there is man page on `git-cliff`), while `git-cliff
--help` does. The former is handled by git, which opens `man 1 git-cliff`,
where as the latter is handled by `git-cliff`, giving out the default help
output from clap.
With this change, `git cliff --help` and `git-cliff --help` still differ, but
at least they both give out a sensible result.
#### 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/39344.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-git-cliff-0.9.0_2-39344.patch --]
[-- Type: text/x-diff, Size: 927 bytes --]
From 6ca72dadd684461223de4cc173398f31115b75e5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20Christian=20Gr=C3=BCnhage?=
<jan.christian@gruenhage.xyz>
Date: Sun, 18 Sep 2022 17:39:26 +0200
Subject: [PATCH] git-cliff: generate and ship man page
---
srcpkgs/git-cliff/template | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/srcpkgs/git-cliff/template b/srcpkgs/git-cliff/template
index b22c7a1a7428..03e99e136092 100644
--- a/srcpkgs/git-cliff/template
+++ b/srcpkgs/git-cliff/template
@@ -1,7 +1,7 @@
# Template file for 'git-cliff'
pkgname=git-cliff
version=0.9.0
-revision=1
+revision=2
archs="x86_64* i686* aarch64* arm*" # ring
build_style=cargo
build_helper=qemu
@@ -23,4 +23,7 @@ post_install() {
vcompletion "_git-cliff" zsh
vcompletion "git-cliff.fish" fish
vcompletion "git-cliff.bash" bash
+
+ OUT_DIR=${PWD} vtargetrun ${DESTDIR}/usr/bin/git-cliff-mangen
+ vman git-cliff.1
}
next reply other threads:[~2022-09-18 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 15:45 jcgruenhage [this message]
2022-09-19 0:00 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39344@inbox.vuxu.org \
--to=jcgruenhage@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).