unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Sean Whitton <spwhitton@spwhitton.name>,
	Protesilaos Stavrou <info@protesilaos.com>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] Add Agitate package
Date: Wed, 28 Sep 2022 07:00:58 -0400	[thread overview]
Message-ID: <CADwFkmkob-5qcz02wuYfiDgj7RLHA7sX0DM_y0qW5bAYthURmw@mail.gmail.com> (raw)
In-Reply-To: <87ill8er5k.fsf@melete.silentflame.com>

Sean Whitton <spwhitton@spwhitton.name> writes:

> In that case, it doesn't make too much sense to me to add it to ELPA,
> but not for the reasons that you give.  It's not that code which is
> targeting emacs.git cannot go on ELPA first, but it seems to me that
> anything on ELPA should be a coherent, singular package.  And Agitate
> isn't that -- it's a collection of functionality that you're filtering
> things out of over time.

FWIW, I don't think this is a very strong reason not to add it.  Other
packages are also grab bags of features, and while perhaps not "ideal"
in an abstract sense, they also provide useful functionality.  In this
case it also makes sense to me to use a package as a way to experiment
with features before they hit core.

We can always delete the package later, once it has done its intended
job and is fully absorbed by Emacs.



  parent reply	other threads:[~2022-09-28 11:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27  6:01 [ELPA] Add Agitate package Protesilaos Stavrou
2022-09-27  8:01 ` Philip Kaludercic
2022-09-27  8:09   ` Protesilaos Stavrou
2022-09-27 16:08 ` Sean Whitton
2022-09-27 17:18   ` Protesilaos Stavrou
2022-09-27 22:07     ` Sean Whitton
2022-09-28  2:14       ` Protesilaos Stavrou
2022-09-28 11:00   ` Stefan Kangas [this message]
2022-09-29  5:52     ` Protesilaos Stavrou
2022-09-29  5:58       ` Protesilaos Stavrou
2022-10-01 22:19       ` Stefan Monnier
2022-10-02  2:07         ` Protesilaos Stavrou
2022-09-30  2:38     ` 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=CADwFkmkob-5qcz02wuYfiDgj7RLHA7sX0DM_y0qW5bAYthURmw@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=info@protesilaos.com \
    --cc=spwhitton@spwhitton.name \
    /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).