From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:40750) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ijzXc-00081b-3k for guix-patches@gnu.org; Wed, 25 Dec 2019 00:49:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ijzXb-0001nD-3y for guix-patches@gnu.org; Wed, 25 Dec 2019 00:49:04 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:47247) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ijzXa-0001mb-8Y for guix-patches@gnu.org; Wed, 25 Dec 2019 00:49:03 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ijzXa-0002ab-66 for guix-patches@gnu.org; Wed, 25 Dec 2019 00:49:02 -0500 Subject: [bug#38738] [PATCH WIP] etc: Add "tarball" snippet. Resent-Message-ID: Received: from eggs.gnu.org ([2001:470:142:3::10]:40119) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ijzWo-0007Za-24 for guix-patches@gnu.org; Wed, 25 Dec 2019 00:48:14 -0500 Received: from fencepost.gnu.org ([2001:470:142:3::e]:55920) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ijzWn-0000rl-T0 for guix-patches@gnu.org; Wed, 25 Dec 2019 00:48:13 -0500 Received: from [2605:6000:1a0d:6320::6a8] (port=39206 helo=oryx) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1ijzWn-0007PJ-54 for guix-patches@gnu.org; Wed, 25 Dec 2019 00:48:13 -0500 From: Brett Gilio Date: Tue, 24 Dec 2019 23:48:16 -0600 Message-ID: <87h81pymzj.fsf@gnu.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: 38738@debbugs.gnu.org --=-=-= Content-Type: text/plain This patch is actually a WIP. I'd ideally like it if it could also detect the addition of `(git-file-name ...)` and add that to the sub-header commit message portion, but I am not so talented in Yasnippet creation :). If anybody wants to take a crack at it, please do. But I think this snippet will prove useful as we will almost always have unstable tarballs coming into our sources. --=-=-= Content-Type: text/x-patch Content-Disposition: inline; filename=0001-etc-Add-tarball-snippet.patch Content-Description: [PATCH] etc: Add "tarball" snippet. >From f4b14a47e3741c107ea83e2717674c8a032f8dba Mon Sep 17 00:00:00 2001 From: Brett Gilio Date: Tue, 24 Dec 2019 23:42:27 -0600 Subject: [PATCH] etc: Add "tarball" snippet. * etc/snippets/text-mode/guix-commit-message-unstable-tarball: New file. --- .../text-mode/guix-commit-message-unstable-tarball | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 etc/snippets/text-mode/guix-commit-message-unstable-tarball diff --git a/etc/snippets/text-mode/guix-commit-message-unstable-tarball b/etc/snippets/text-mode/guix-commit-message-unstable-tarball new file mode 100644 index 0000000000..e82f522e54 --- /dev/null +++ b/etc/snippets/text-mode/guix-commit-message-unstable-tarball @@ -0,0 +1,8 @@ +# -*- mode: snippet -*- +# name: guix-commit-message-unstable-tarball +# key: tarball +# condition: git-commit-mode +# -- +gnu: $1: Don't use unstable tarball. + +* `(car (magit-staged-files))` ($1)[source]: Download using GIT-FETCH. \ No newline at end of file -- 2.24.1 --=-=-=--