From: Oleg Pykhalov <go.wigust@gmail.com>
To: 34865-done@debbugs.gnu.org
Cc: Brian Leung <bkleung89@gmail.com>
Subject: bug#34865: [PATCH] Add emacs-zones.
Date: Wed, 27 Mar 2019 22:27:39 +0300 [thread overview]
Message-ID: <87y350ruc4.fsf@gmail.com> (raw)
In-Reply-To: <87va04fuul.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 27 Mar 2019 11:57:22 +0100")
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
Hello,
Ludovic Courtès <ludo@gnu.org> writes:
[…]
>>>>>> Could we use emacs-zones from Elpa? See
>>>>>> https://elpa.gnu.org/packages/zones.html . ‘guix import elpa
>>>>>> emacs-zones’ will produce a decent ‘origin’ record to pull a source.
>>>>>
>>>>> My understanding is that ELPA and MELPA tarballs are not necessarily
>>>>> persistent and immutable, and that we generally prefer referring
>>>>> directly to the upstream repo.
>>>>
>>>> Ouch, I thought ELPA is persistent. That's a significant argument to
>>>> not use ELPA for our purposes :-( .
>>
>> I only know that MELPA isn’t immutable. I assumed that ELPA is fine.
>
> [...]
>
>> git-fetch is the preferred way when there are no stable tarballs.
>
> So, Oleg, I think you can go either way, but fetching over Git is
> probably safer.
>
> Can you apply the patch?
OK, pushed as c881ed8698517a2c2007c2fdc3a7aeec52ff109c with a source
fetching over Git.
Thanks,
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2019-03-27 19:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 0:24 [bug#34865] [PATCH] Add emacs-zones Brian Leung
2019-03-16 10:56 ` Oleg Pykhalov
2019-03-22 21:37 ` Ludovic Courtès
2019-03-24 20:01 ` Oleg Pykhalov
2019-03-26 9:39 ` Ludovic Courtès
2019-03-26 10:55 ` Ricardo Wurmus
2019-03-27 10:57 ` Ludovic Courtès
2019-03-27 19:27 ` Oleg Pykhalov [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y350ruc4.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=34865-done@debbugs.gnu.org \
--cc=bkleung89@gmail.com \
/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.