From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, ane@iki.fi, emacs-devel@gnu.org
Subject: Re: NonGNU ELPA and release frequency
Date: Sat, 24 Oct 2020 17:12:13 +0300 [thread overview]
Message-ID: <X5Q2PYIrwublip67@protected.rcdrun.com> (raw)
In-Reply-To: <83k0vfhjiu.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2020-10-24 15:55]:
> > Date: Sat, 24 Oct 2020 05:06:25 -0700
> > From: Jean Louis <bugs@rcdrun.com>
> > Cc: rms@gnu.org, ane@iki.fi, emacs-devel@gnu.org
> >
> > On Sat, Oct 24, 2020 at 11:41:47AM +0300, Eli Zaretskii wrote:
> > > > Date: Sat, 24 Oct 2020 10:08:04 +0300
> > > > From: Jean Louis <bugs@gnu.support>
> > > > Cc: Antoine Kalmbach <ane@iki.fi>, emacs-devel@gnu.org
> > > >
> > > > My proposals for plan of action for ELPA on nongnu.org are following,
> > > > and they are not in any order:
> > >
> > > Would you like to volunteer to do some or all of this?
> >
> > I am ready.
>
> Thank you; please go ahead.
Tell me next steps.
On my side I am already making my personal review of packages and
making list of those wrapping non-free packages, and sorting them,
looking inside, compiling and looking which are useful. I will come up
with my list soon.
So far there is about 20 that are made for non-free software or that
would drive users to non-free, but I have just started reviewing it.
next prev parent reply other threads:[~2020-10-24 14:12 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 11:59 NonGNU ELPA and release frequency Antoine Kalmbach
2020-10-23 12:24 ` Stefan Kangas
2020-10-23 18:25 ` Antoine Kalmbach
2020-10-24 3:45 ` Richard Stallman
2020-10-24 13:51 ` Antoine Kalmbach
2020-10-26 9:56 ` Philip K.
2020-10-27 3:41 ` Richard Stallman
2020-10-24 3:50 ` Richard Stallman
2020-10-24 7:08 ` Jean Louis
2020-10-24 8:41 ` Eli Zaretskii
2020-10-24 12:06 ` Jean Louis
2020-10-24 12:54 ` Eli Zaretskii
2020-10-24 14:12 ` Jean Louis [this message]
2020-10-24 14:16 ` Eli Zaretskii
2020-10-24 14:21 ` NonGNU ELPA Jean Louis
2020-10-24 14:50 ` Eli Zaretskii
2020-10-24 14:25 ` NonGNU ELPA and release frequency Antoine Kalmbach
2020-10-24 14:29 ` NonGNU ELPA Jean Louis
2020-10-24 14:40 ` Antoine Kalmbach
2020-10-24 16:37 ` Michael Albinus
2020-10-24 17:05 ` Stefan Kangas
2020-10-24 18:00 ` Antoine Kalmbach
2020-10-24 19:12 ` Michael Albinus
2020-10-25 11:40 ` Michael Albinus
2020-10-25 12:20 ` Antoine Kalmbach
2020-10-25 3:48 ` NonGNU ELPA and release frequency Richard Stallman
2020-10-25 10:29 ` Dmitry Gutov
2020-10-25 13:50 ` Stefan Monnier
2020-10-25 14:54 ` Ivan Yonchovski
2020-10-25 15:15 ` Antoine Kalmbach
2020-10-26 4:10 ` Richard Stallman
2020-10-26 10:35 ` NonGNU ELPA Jean Louis
2020-10-27 3:47 ` Richard Stallman
2020-10-26 17:37 ` NonGNU ELPA and release frequency Dmitry Gutov
2020-10-27 3:45 ` Richard Stallman
2020-10-25 3:48 ` Richard Stallman
2020-10-24 18:47 ` Stefan Monnier
2020-10-26 4:10 ` Richard Stallman
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=X5Q2PYIrwublip67@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=ane@iki.fi \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/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).