From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "Jonathan Scoresby" <me@jonscoresby.com>, <60029@debbugs.gnu.org>
Subject: [bug#60029] [PATCH 2/4] gnu: vim: add relevant locations to 'package-path' instead of 'runtime-path'
Date: Wed, 14 Dec 2022 06:56:54 +0000 [thread overview]
Message-ID: <CP1CF8FDW6LZ.KHQDBP78ZQK8@guix-framework> (raw)
In-Reply-To: <1132100161.39616.1670969401671@office.mailbox.org>
[-- Attachment #1: Type: text/plain, Size: 177 bytes --]
On Tue Dec 13, 2022 at 10:10 PM GMT, Jonathan Scoresby wrote:
> Sorry, do you mean to the commit message or to the file itself?
To the commit message, please.
-- (
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-12-14 6:58 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 [this message]
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 ` bug#60029: [PATCH v3 0/3] Add vim-build-system Efraim Flashner
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=CP1CF8FDW6LZ.KHQDBP78ZQK8@guix-framework \
--to=guix-patches@gnu.org \
--cc=60029@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.