GNU bug report logs - #35680
[PATCH] Update Neovim to version 0.3.5

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Arun Isaac <arunisaac <at> systemreboot.net>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#35680: closed ([PATCH] Update Neovim to version 0.3.5)
Date: Sat, 11 May 2019 07:34:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Sat, 11 May 2019 13:03:21 +0530
with message-id <cu7r295a1j2.fsf <at> systemreboot.net>
and subject line Re: [bug#35680] [PATCH] Update Neovim to version 0.3.5
has caused the debbugs.gnu.org bug report #35680,
regarding [PATCH] Update Neovim to version 0.3.5
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
35680: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=35680
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: HiPhish <hiphish <at> posteo.de>
To: guix-patches <at> gnu.org
Subject: [PATCH] Update Neovim to version 0.3.5
Date: Sat, 11 May 2019 00:01:51 +0200

[Message part 3 (text/plain, inline)]

This patch updates Neovim to the current version. As a side note, there is a 
TODO from the previous definition to remove an in-place patching when the 
package definition gets updated; the fix is not in 0.3.5, so I have not removed 
this part of the defintion on purpose, it is not an oversight.

[0001-gnu-packages-vim.scm-neovim-Update-to-v0.3.5.patch (text/x-patch, attachment)]

[Message part 5 (message/rfc822, inline)]

From: Arun Isaac <arunisaac <at> systemreboot.net>
To: HiPhish <hiphish <at> posteo.de>
Cc: 35680-done <at> debbugs.gnu.org
Subject: Re: [bug#35680] [PATCH] Update Neovim to version 0.3.5
Date: Sat, 11 May 2019 13:03:21 +0530

[Message part 6 (text/plain, inline)]

Thanks! I've pushed the patch with the following modifications.

- I changed the commit message to conform to our conventions. (Hint: If
  you're using emacs, you can generate this commit message easily using
  the yasnippets provided under etc/snippets in the Guix source tree.
- I changed the source to use git-fetch. GitHub's autogenerated source
  tarballs are unstable, and we should prefer git-fetch in such
  cases. Notice that `guix lint' also warns of this.
- I added a copyright header for you.

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.