From: Marius Bakke <mbakke@fastmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: vim: Update to 8.0.0047.
Date: Fri, 28 Oct 2016 20:57:14 +0100 [thread overview]
Message-ID: <874m3wtffp.fsf@duckhunt.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87shrgjt33.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
Ricardo Wurmus <rekado@elephly.net> writes:
>>> Guix can handle downloading patches, so there’s really no need for
>>> switching in my opinion. “gnu/packages/bash.scm” could be used as a
>>> reference for how to deal with a large number of patches.
>>
>> vim-7.4 ended at 2367 patches[0]. 8.0 is currently at 51 (four since
>> yesterday!), whereas bash has 42, so they are not really comparable. I
>> think vim would rarely be updated, if it required downloading and
>> creating potentially hundreds of patch references at once.
>>
>> They are also not signed, though we could rely on the MD5SUMS file.
>>
>> With this information, do you still think a custom patch importer is
>> better? I don't really mind either way, but someone needs to make it :)
>
> No, you convinced me :) Thanks for your patience!
Thanks for questioning my oft-rushed conclusions! :)
I updated vim in a9afb956b3232ccfb7deaf3feed02b60a12d65bf.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 454 bytes --]
prev parent reply other threads:[~2016-10-28 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 13:29 [PATCH] gnu: vim: Update to 8.0.0047 Marius Bakke
2016-10-27 20:20 ` ng0
2016-10-28 6:02 ` Ricardo Wurmus
2016-10-28 7:19 ` ng0
2016-10-28 16:55 ` Marius Bakke
2016-10-28 17:12 ` Ricardo Wurmus
2016-10-28 19:57 ` Marius Bakke [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=874m3wtffp.fsf@duckhunt.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).