From: Stefan Kangas <stefankangas@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, Po Lu <luangruo@yahoo.com>
Cc: Philip Kaludercic <philipk@posteo.net>,
emacs-devel@gnu.org, Jonas Bernoulli <jonas@bernoul.li>
Subject: Re: master d506d91b1f 2/2: Make linum.el obsolete
Date: Thu, 22 Sep 2022 07:01:24 -0700 [thread overview]
Message-ID: <CADwFkmmMvgQVznfr4fjYq9SvRU2VZ0-jqXLLAFHuPeWVaYMY8g@mail.gmail.com> (raw)
In-Reply-To: <jwvy1ubmt89.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> We already have some left-over branches in `elpa.git` for packages which
> we don't actually distribute any more (W3, mainly). We could try and
> make that more "formal" and easier to find.
IMO, it would be best to avoid littering GNU ELPA with unmaintained
libraries. So if we want to do that, they should be separated out from
the main archive somehow.
next prev parent reply other threads:[~2022-09-22 14:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166370103866.17769.3203831255447980421@vcs2.savannah.gnu.org>
[not found] ` <20220920191039.C61BCC00874@vcs2.savannah.gnu.org>
2022-09-21 7:50 ` master d506d91b1f 2/2: Make linum.el obsolete Philip Kaludercic
2022-09-21 8:37 ` Stefan Kangas
2022-09-21 9:45 ` Philip Kaludercic
2022-09-21 12:35 ` Stefan Kangas
2022-09-21 12:43 ` Philip Kaludercic
2022-09-21 13:58 ` Stefan Kangas
2022-09-21 16:13 ` [External] : " Drew Adams
2022-09-21 16:36 ` Stefan Kangas
2022-09-21 18:26 ` Philip Kaludercic
2022-09-21 19:19 ` Stefan Kangas
2022-09-22 2:59 ` Po Lu
2022-09-22 11:01 ` Stefan Kangas
2022-09-22 11:50 ` Po Lu
2022-09-22 13:31 ` Stefan Monnier
2022-09-22 14:01 ` Stefan Kangas [this message]
2022-09-22 14:15 ` Stefan Monnier
2022-09-21 16:17 ` chad
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmmMvgQVznfr4fjYq9SvRU2VZ0-jqXLLAFHuPeWVaYMY8g@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jonas@bernoul.li \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.