Hello Stefan again,

now emacs-async master is compliant with elpa (package-requires, no
pkg.el file), so now I can push from master to elpa, my remote called
elpa is pointing to "me@git.sv$gnu.org:/srv/git/emacs/elpa.git", can I
push safely with git push elpa master:refs/heads/externals/async?

Thanks.

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> [[PGP Encrypted Part:OK]]
>> Yes, the name I use -elpa- is bad,
>
> Really?  It sounds like a genuinely natural and intuitive choice to me ;-)
>
>> but yes a repository per repo would be great, in github organizations
>> allow having one repo per package like in helm organization.
>
> I know it's more traditional and has its advantages, but currently it's
> not really an option.
>
>> What about ((emacs "24.4")) we don't care of 24.3, we are at 27.2 now so
>> very far from 24.3.
>
> ((emacs "24.4")) would work, yes.  Whether that's better than
> ((emacs "24.3") (nadvice "0.3")) or even ((cl-lib "0.5") (nadvice "0.3"))
> is for the maintainers of Async to decide ;-)
>
>>> - The `async-pkg.el` which is absent on `elpa` and present on `master`.
>>>   Do we actually need it on `master`?
>> IIRC yes, Melpa needs it.
>
> Why would it matter, since it's on GNU ELPA anyway?
>
>
>         Stefan
>
>
>
>
> [[End of PGP Encrypted Part]]


-- 
Thierry