Processing control commands:
> reassign -1 emacs-pg-el
Bug #1093398 [elpa-emacsql-psql] elpa-emacsql-psql: Depending on the wrong pg.el
Bug reassigned from package 'elpa-emacsql-psql' to 'emacs-pg-el'.
No longer marked as found in versions emacsql/4.1.0-1.
Ignoring request to alter fixed versions
Control: reassign -1 emacs-pg-el
Control: found -1 0.13+git.20130731.456516ec-3
Xiyue Deng writes:
> Xiyue Deng writes:
>
>> Hi Aymeric,
>>
>> Great to hear back from you! Please see my reply below.
>>
>> Aymeric Agon-Rambosson writes:
>>
>>> Hi,
>>>
>>> Sorry for the late answer.
>>>
>>> I a
Xiyue Deng writes:
> Hi Aymeric,
>
> Great to hear back from you! Please see my reply below.
>
> Aymeric Agon-Rambosson writes:
>
>> Hi,
>>
>> Sorry for the late answer.
>>
>> I am confused. If the upstream of package pg-el changed, can we
>> just not follow that new upstream and pull from it
Hi Aymeric,
Great to hear back from you! Please see my reply below.
Aymeric Agon-Rambosson writes:
> Hi,
>
> Sorry for the late answer.
>
> I am confused. If the upstream of package pg-el changed, can we
> just not follow that new upstream and pull from it ? This is what
> I usually do when
Hi,
Sorry for the late answer.
I am confused. If the upstream of package pg-el changed, can we
just not follow that new upstream and pull from it ? This is what
I usually do when upstream changes.
You are saying https://github.com/emarsden/pg-el (new) and
https://github.com/cbbrowne/pg.el
Xiyue Deng writes:
> Xiyue Deng writes:
>
>> FYI I have implemented the dropping pg-el part in a "drop-pg-el" branch
>> on Salsa[1]. The diff can be found at [2]. If this looks OK I'll apply
>> this on the master branch following the git-debrebase workflow and ask
>> for sponsorship.
>>
>> [1]
6 matches
Mail list logo
