From: Efraim Flashner <efraim@flashner.co.il>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Updating Vim
Date: Wed, 9 Mar 2016 12:35:17 +0200 [thread overview]
Message-ID: <20160309123517.29f7cb9e@debian-netbook> (raw)
In-Reply-To: <20160309094544.GA28981@solar>
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
On Wed, 9 Mar 2016 10:45:44 +0100
Andreas Enge <andreas@enge.fr> wrote:
> On Wed, Mar 09, 2016 at 11:16:16AM +0200, Efraim Flashner wrote:
> [...]
>
> Well, it is not quite a release, I would say, if they simply tag every git
> commit and do not even make sure that the tests succeed each time. Normally,
> our policy in guix is to follow "official" upstream releases.
>
> Is there a compelling reason to update nevertheless?
>
> Andreas
>
There was something that was not interacting well with my .vimrc, but I just
checked with 7.4 and 7.4.963 and there wasn't actually a change. Either I
stopped using some plugin that wanted a newer version or I misread it before.
"Because its 2 years old" isn't a great reason. There is a list of patches
with a 1-liner[1] for what it fixes, so I suppose for that it would be good
to have those issues taken care of, and also to have our copy of vim more
up-to-date with other distros.
[1] ftp://ftp.vim.org/pub/vim/patches/7.4/README
--
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: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-03-09 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 9:16 Updating Vim Efraim Flashner
2016-03-09 9:39 ` Ricardo Wurmus
2016-03-09 9:41 ` Efraim Flashner
2016-03-09 9:45 ` Andreas Enge
2016-03-09 10:35 ` 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=20160309123517.29f7cb9e@debian-netbook \
--to=efraim@flashner.co.il \
--cc=andreas@enge.fr \
--cc=guix-devel@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).