[debbugs-tracker] bug#34865: closed ([PATCH] Add emacs-zones.)

[GNU bug Tracking System]

Your message dated Wed, 27 Mar 2019 22:27:39 +0300
with message-id <address@hidden>
and subject line Re: [bug#34865] [PATCH] Add emacs-zones.
has caused the debbugs.gnu.org bug report #34865,
regarding [PATCH] Add emacs-zones.
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
34865: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=34865
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: [PATCH] Add emacs-zones. Date: Fri, 15 Mar 2019 01:24:08 +0100

See attached.

0001-gnu-Add-emacs-zones.patch
Description: Text Data

--- End Message ---

--- Begin Message --- Subject: Re: [bug#34865] [PATCH] Add emacs-zones. Date: Wed, 27 Mar 2019 22:27:39 +0300 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)

Hello,

Ludovic Courtès <address@hidden> 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.

signature.asc
Description: PGP signature

--- End Message ---