From: Imran Iqbal <imran@imraniqbal.org>
To: 54981@debbugs.gnu.org
Subject: [bug#54981] [PATCH 0/3] Update neovim to version 0.7.0
Date: Sat, 16 Apr 2022 23:34:13 -0400 [thread overview]
Message-ID: <20220417033416.333057-1-imran@imraniqbal.org> (raw)
Hi,
This set of patches brings neovim up to version 0.7.0. A change was
introduced:
https://github.com/neovim/neovim/commit/55ab76a1c0f63ebb735495a91066cbe01b6d0bb3
that bumps the required version lua-luv to 1.43.0-0, which subsequently
required libuv to bumped to 1.43.0 as well.
lua-compat-5.3 was bumped to e245d3a18957e43ef902a59a72c8902e2e4435b9
which moves the compat-5.3.h header file under a new c-api folder see:
https://github.com/luvit/luv/commit/60946d35ad6ba80d836e70174e0610ed32c3eb01
next prev reply other threads:[~2022-04-17 5:19 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 17:46 [bug#55045] [PATCH] update neovim to 0.7.0 Luis Henrique Gomes Higino
2022-04-20 17:52 ` [bug#55045] [PATCH 1/4] gnu: lua-luv: Update to 1.43.0-0 Luis Henrique Gomes Higino
2022-04-20 17:52 ` [bug#55045] [PATCH 2/4] gnu: lua-luv: replace sexps with gexps Luis Henrique Gomes Higino
2022-04-20 17:52 ` [bug#55045] [PATCH 3/4] gnu: neovim: Update to 0.7.0 Luis Henrique Gomes Higino
2022-04-20 17:52 ` [bug#55045] [PATCH 4/4] gnu: neovim: replace sexps with gexps Luis Henrique Gomes Higino
2022-04-21 2:47 ` [bug#55045] [PATCH] update neovim to 0.7.0 Imran Iqbal
2022-04-22 1:07 ` Luis Henrique Gomes Higino
2022-04-28 22:35 ` Ludovic Courtès
2022-05-05 15:02 ` Luis Henrique Gomes Higino
2022-05-17 22:49 ` Imran Iqbal
2022-05-17 23:01 ` Luis Henrique Gomes Higino
2022-05-17 23:16 ` [bug#55045] [PATCH v2 1/4] gnu: lua-luv: Update to 1.43.0-0 Luis Henrique Gomes Higino
2022-05-17 23:16 ` [bug#55045] [PATCH v2 2/4] gnu: lua-luv: Use gexps Luis Henrique Gomes Higino
2022-05-17 23:16 ` [bug#55045] [PATCH v2 3/4] gnu: neovim: Update to 0.7.0 Luis Henrique Gomes Higino
2022-05-17 23:16 ` [bug#55045] [PATCH v2 4/4] gnu: neovim: Use new style Luis Henrique Gomes Higino
2022-05-18 11:09 ` Maxime Devos
2022-05-18 12:06 ` Luis Henrique Gomes Higino
2022-05-18 13:32 ` [bug#55045] [PATCH v3 1/4] gnu: lua-luv: Update to 1.43.0-0 Luis Henrique Gomes Higino
2022-05-18 13:32 ` [bug#55045] [PATCH v3 2/4] gnu: lua-luv: Use gexps Luis Henrique Gomes Higino
2022-05-18 13:32 ` [bug#55045] [PATCH v3 3/4] gnu: neovim: Update to 0.7.0 Luis Henrique Gomes Higino
2022-05-18 13:32 ` [bug#55045] [PATCH v3 4/4] gnu: neovim: Use new style Luis Henrique Gomes Higino
2022-05-18 18:12 ` bug#55045: [PATCH] update neovim to 0.7.0 Ludovic Courtès
2022-04-17 3:34 ` Imran Iqbal [this message]
2022-04-17 3:34 ` [bug#54982] [PATCH 1/3] gnu: libuv: Update to 1.43.0 Imran Iqbal
2022-04-17 5:18 ` bug#54982: Acknowledgement ([PATCH 1/3] gnu: libuv: Update to 1.43.0.) GNU bug Tracking System
2022-05-18 18:13 ` bug#54982: closed (Re: bug#55045: [PATCH] update neovim to 0.7.0) GNU bug Tracking System
2022-04-17 3:34 ` [bug#54983] [PATCH 2/3] gnu: lua-luv: Update to 1.43.0-0 Imran Iqbal
2022-04-17 5:18 ` bug#54983: Acknowledgement ([PATCH 2/3] gnu: lua-luv: Update to 1.43.0-0.) GNU bug Tracking System
2022-05-18 18:13 ` bug#54983: closed (Re: bug#55045: [PATCH] update neovim to 0.7.0) GNU bug Tracking System
2022-04-17 3:34 ` [bug#54984] [PATCH 3/3] gnu: neovim: Update to 0.7.0 Imran Iqbal
2022-04-17 5:18 ` bug#54984: Acknowledgement ([PATCH 3/3] gnu: neovim: Update to 0.7.0.) GNU bug Tracking System
2022-05-18 18:13 ` bug#54984: closed (Re: bug#55045: [PATCH] update neovim to 0.7.0) GNU bug Tracking System
2022-04-17 5:18 ` bug#54981: Acknowledgement ([PATCH 0/3] Update neovim to version 0.7.0) GNU bug Tracking System
2022-04-17 8:07 ` [bug#54981] [PATCH 0/3] Update neovim to version 0.7.0 Maxime Devos
2022-05-18 18:13 ` bug#54981: closed (Re: bug#55045: [PATCH] update neovim to 0.7.0) GNU bug Tracking System
2022-05-18 13:35 ` [bug#55045] About trailing #t Luis Henrique Gomes Higino
2022-05-18 18:33 ` Tobias Geerinckx-Rice via Guix-patches via
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=20220417033416.333057-1-imran@imraniqbal.org \
--to=imran@imraniqbal.org \
--cc=54981@debbugs.gnu.org \
--cc=guix-patches@gnu.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).