From: Efraim Flashner <efraim@flashner.co.il>
To: 60029-done@debbugs.gnu.org
Cc: paren@disroot.org, me@jonscoresby.com
Subject: bug#60029: [PATCH v3 0/3] Add vim-build-system.
Date: Wed, 8 Nov 2023 12:16:11 +0200 [thread overview]
Message-ID: <ZUtf63BVnFaliok3@3900XT> (raw)
In-Reply-To: <cover.1697446927.git.efraim@flashner.co.il>
[-- Attachment #1: Type: text/plain, Size: 428 bytes --]
I did another round of review on the patches (which did find some
things) and I've now pushed these patches!
Now I have to figure out how to use packadd so I can drop
editorconfig-vim since it comes with vim.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-11-08 10:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 0:38 [bug#60029] [PATCH core-updates 0/4] vim-build-system Jonathan Scoresby
2022-12-13 8:34 ` [bug#60029] [PATCH 1/4] guix: copy-build-system: allow install plan directives to specify output Jonathan Scoresby
2022-12-13 19:05 ` ( via Guix-patches via
2022-12-13 8:34 ` [bug#60029] [PATCH 2/4] gnu: vim: add relevant locations to 'package-path' instead of 'runtime-path' Jonathan Scoresby
2022-12-13 19:06 ` ( via Guix-patches via
2022-12-13 22:10 ` Jonathan Scoresby
2022-12-14 6:56 ` ( via Guix-patches via
2022-12-13 8:34 ` [bug#60029] [PATCH 3/4] guix: add vim-build-system Jonathan Scoresby
2022-12-13 8:34 ` [bug#60029] [PATCH 4/4] gnu: have vim packages use vim-build-system Jonathan Scoresby
2022-12-14 21:01 ` [bug#60029] [PATCH v2 1/4] guix: copy-build-system: allow install plan directives to specify output Jonathan Scoresby
2022-12-14 21:02 ` [bug#60029] [PATCH v2 2/4] gnu: vim: add relevant locations to 'package-path' instead of 'runtime-path' Jonathan Scoresby
2022-12-14 21:14 ` ( via Guix-patches via
2022-12-14 21:02 ` [bug#60029] [PATCH v2 3/4] guix: add vim-build-system Jonathan Scoresby
2022-12-14 21:02 ` [bug#60029] [PATCH v2 4/4] gnu: have vim packages use vim-build-system Jonathan Scoresby
2023-10-16 9:15 ` [bug#60029] [PATCH v3 0/3] Add vim-build-system Efraim Flashner
2023-10-16 9:15 ` [bug#60029] [PATCH v3 1/3] gnu: vim: Add vim packages to 'package-path' instead of 'runtime-path' Efraim Flashner
2023-10-16 9:15 ` [bug#60029] [PATCH v3 2/3] build-system: Add vim-build-system Efraim Flashner
2023-10-16 9:15 ` [bug#60029] [PATCH v3 3/3] gnu: Have vim packages use vim-build-system Efraim Flashner
2023-11-08 10:16 ` Efraim Flashner [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZUtf63BVnFaliok3@3900XT \
--to=efraim@flashner.co.il \
--cc=60029-done@debbugs.gnu.org \
--cc=me@jonscoresby.com \
--cc=paren@disroot.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).