From: jgarte <jgarte@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: git-interactive-rebase-tool
Date: Sat, 17 Jul 2021 02:42:25 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32013@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
There is a new pull request by jgarte against master on the void-packages repository
https://github.com/jgarte/void-packages git-interactive-rebase-tool
https://github.com/void-linux/void-packages/pull/32013
New package: git-interactive-rebase-tool
#### General
- [ x] 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
#### Does it build and run successfully?
- [x ] I built this PR locally for my native architecture, (i386)
A patch file from https://github.com/void-linux/void-packages/pull/32013.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-git-interactive-rebase-tool-32013.patch --]
[-- Type: text/x-diff, Size: 1147 bytes --]
From e935de0deae3d6db8a6ae284bfb77bc38714a463 Mon Sep 17 00:00:00 2001
From: jgart <jgart@dismail.de>
Date: Fri, 16 Jul 2021 20:35:58 -0400
Subject: [PATCH] New package: git-interactive-rebase-tool
---
srcpkgs/git-interactive-rebase-tool/template | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
create mode 100644 srcpkgs/git-interactive-rebase-tool/template
diff --git a/srcpkgs/git-interactive-rebase-tool/template b/srcpkgs/git-interactive-rebase-tool/template
new file mode 100644
index 000000000000..6d7cacb6f5d8
--- /dev/null
+++ b/srcpkgs/git-interactive-rebase-tool/template
@@ -0,0 +1,16 @@
+# Template file for 'git-interactive-rebase-tool'
+pkgname=git-interactive-rebase-tool
+version=2.1.0
+revision=1
+#archs="i686 x86_64"
+build_style=cargo
+short_desc="Terminal based sequence editor for git interactive rebase"
+maintainer="jgart <jgart@dismail.de>"
+license="GPL-3.0-or-later"
+homepage="https://gitrebasetool.mitmaro.ca"
+distfiles="https://github.com/MitMaro/${pkgname}/archive/refs/tags/${version}.tar.gz"
+checksum=@e82a7446af7f581fc2a2900042916cfe323778929aa804488e4b274486733557
+
+do_check() {
+ cargo test
+}
next reply other threads:[~2021-07-17 0:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-17 0:42 jgarte [this message]
2021-07-17 0:49 ` [PR PATCH] [Updated] " jgarte
2021-07-17 1:09 ` [PR REVIEW] " ericonr
2021-07-17 1:09 ` jgarte
2021-07-17 1:10 ` [PR REVIEW] " jgarte
2021-07-17 1:15 ` jgarte
2021-07-17 1:17 ` sgn
2021-07-17 1:27 ` ericonr
2021-07-17 1:38 ` jgarte
2021-07-17 1:39 ` jgarte
2021-07-17 2:42 ` jgarte
2021-07-17 2:45 ` [PR PATCH] [Updated] " jgarte
2021-07-17 2:58 ` [PR REVIEW] " jgarte
2021-11-18 21:24 ` [PR PATCH] [Closed]: " jgarte
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-32013@inbox.vuxu.org \
--to=jgarte@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).