Hi Sean,
Пт 21 дек 2018 @ 12:15 Sean Whitton :
> On Wed 05 Dec 2018 at 01:14pm +0500, Lev Lamberov wrote:
>
>> So, sticking to stable MELPA version will not require splitting the
>> source code into several source packages.
>
> Indeed.
>
>> Should I patch Version (change it everywhere to 2.4) or
Hello Lev,
On Wed 05 Dec 2018 at 01:14pm +0500, Lev Lamberov wrote:
> So, sticking to stable MELPA version will not require splitting the
> source code into several source packages.
Indeed.
> Should I patch Version (change it everywhere to 2.4) or include
> Package-Version (as it is done in MEL
Hi Sean,
Вт 18 дек 2018 @ 17:31 Sean Whitton :
> On Sat 08 Dec 2018 at 11:16am +0500, Lev Lamberov wrote:
>
>> Пт 07 дек 2018 @ 18:46 Sean Whitton :
>>>
>>> To confirm, are you saying that MELPA has added Package-Version headers,
>>> overriding the Version: headers from upstream, such that everyt
Hello Lev,
On Sat 08 Dec 2018 at 11:16am +0500, Lev Lamberov wrote:
> Пт 07 дек 2018 @ 18:46 Sean Whitton :
>>
>> To confirm, are you saying that MELPA has added Package-Version headers,
>> overriding the Version: headers from upstream, such that everything in
>> 2.4? What about the libs in your
Пт 07 дек 2018 @ 18:46 Sean Whitton :
> Thank you for working on this.
>
> On Wed 05 Dec 2018 at 01:14PM +0500, Lev Lamberov wrote:
>
>> Now it became a bit more complicated. So, there's 2.4 release, which
>> contains the following Emacs Lisp files (declared Version included, no
>> Package-Version
Hello Lev,
Thank you for working on this.
On Wed 05 Dec 2018 at 01:14PM +0500, Lev Lamberov wrote:
> Now it became a bit more complicated. So, there's 2.4 release, which
> contains the following Emacs Lisp files (declared Version included, no
> Package-Version declaration in the original source
6 matches
Mail list logo
