From: Thierry Volpiatto <thievol@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: updating async on elpa
Date: Sat, 01 May 2021 15:37:51 +0000 [thread overview]
Message-ID: <87h7jm5u7w.fsf@posteo.net> (raw)
In-Reply-To: <jwvmtte620q.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 686 bytes --]
next prev parent reply other threads:[~2021-05-01 15:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 11:56 updating async on elpa Thierry Volpiatto
2021-04-30 14:17 ` Stefan Monnier
2021-04-30 15:20 ` Thierry Volpiatto
2021-04-30 16:21 ` Stefan Monnier
2021-04-30 17:42 ` Thierry Volpiatto
2021-04-30 18:36 ` Stefan Monnier
2021-04-30 18:42 ` Stefan Monnier
2021-04-30 18:37 ` Thierry Volpiatto
2021-04-30 18:48 ` Stefan Monnier
2021-04-30 19:31 ` Thierry Volpiatto
2021-04-30 20:21 ` Stefan Monnier
2021-05-01 4:45 ` Thierry Volpiatto
2021-05-01 13:05 ` Yoni Rabkin
2021-05-01 14:22 ` Stefan Monnier
2021-05-01 14:50 ` Thierry Volpiatto
2021-05-01 15:49 ` Stefan Monnier
2021-05-02 20:26 ` (was Re: updating async on elpa) auto-sync for emms Yoni Rabkin
2021-05-03 13:39 ` Stefan Monnier
2021-05-01 13:06 ` updating async on elpa Stefan Monnier
2021-05-01 14:38 ` Thierry Volpiatto
2021-05-01 15:37 ` Thierry Volpiatto [this message]
2021-05-01 17:11 ` Stefan Monnier
2021-05-01 18:01 ` Thierry Volpiatto
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7jm5u7w.fsf@posteo.net \
--to=thievol@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).