From: phillip.lord@russet.org.uk (Phillip Lord)
To: Richard Stallman <rms@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: In Support of ELPA
Date: Fri, 14 Jul 2017 11:02:43 +0100 [thread overview]
Message-ID: <87bmonnxoc.fsf@russet.org.uk> (raw)
In-Reply-To: <E1dVpGy-0002Lk-Ht@fencepost.gnu.org> (Richard Stallman's message of "Thu, 13 Jul 2017 21:20:00 -0400")
Richard Stallman <rms@gnu.org> writes:
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> > If the outside host is someone who has write access to ELPA does it make
> > any difference?
>
> The difference is whether the Emacs maintainers have write access
> to those sources in their main repository.
Personally, I think this is not necessary. The Emacs maintainers can use
PRs if they need to.
Ultimately, if we accept the notion of a "downstream" it's far easier to
make all changes there, rather than have to manage changes from two
places. The ELPA repo isn't really set up well for development: it has a
large number of independent projects in one place, and uses branches for
something else.
Reducing the friction of ELPA would include removing the necessity for
changing the version control practices of existing projects.
Phil
next prev parent reply other threads:[~2017-07-14 10:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 21:46 In Support of ELPA Phillip Lord
2017-07-11 22:37 ` Stefan Monnier
2017-07-12 13:30 ` Ted Zlatanov
2017-07-13 12:23 ` Richard Stallman
2017-07-13 15:05 ` Ted Zlatanov
2017-07-13 22:02 ` Phillip Lord
2017-07-13 16:15 ` Phillip Lord
2017-07-14 1:20 ` Richard Stallman
2017-07-14 10:02 ` Phillip Lord [this message]
2017-07-16 1:50 ` Richard Stallman
2017-07-17 14:05 ` Phillip Lord
2017-07-14 2:12 ` Stefan Monnier
2017-07-14 6:48 ` Thien-Thi Nguyen
2017-07-15 1:35 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bmonnxoc.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--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 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.