all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Improving GNU ELPA
Date: Tue, 18 Jul 2017 17:17:02 +0100	[thread overview]
Message-ID: <87y3rloh35.fsf@russet.org.uk> (raw)
In-Reply-To: <jwvshhtuawo.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Tue, 18 Jul 2017 09:35:52 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> If I could push to upstream, it would be simpler, but still require
>> merges.
>
> AFAIU, what you mean by "merges" is simply the result of changes being
> made both to the github repository and to the elpa.git repository.
> It's unrelated to how the copy of dash kept on the gnu.org side is
> stored (a subtree, or a separate branchm or a separate repository) as
> long as it can be modified on the gnu.org side.
>
> Right?

I think so, yes. I've never used subtrees. Orphan branches in a repo are
essentially the same as a separate repo except that they share a
namespace for branches and tags. So, I guess, with a separate repo you
could do things like make a feature branch and then PR for this
upstream.

But in terms of use, not modifying the gnu.org side (except in
exceptional circumstances) would make the use of ELPA with an upstream
repo easier. ELPA would, effectively, operate like Jonas' emacsmirror;
there in case the upstream disappeared.

Phil



  reply	other threads:[~2017-07-18 16:17 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-08  1:59 Adding advisory notification for non-ELPA package.el downloads John Wiegley
2017-07-08 10:29 ` Dmitry Gutov
2017-07-08 12:57   ` Kaushal Modi
2017-07-08 17:03   ` Richard Stallman
2017-07-08 22:12     ` Jean-Christophe Helary
2017-07-08 22:50       ` Tim Cross
2017-07-10  9:29         ` Richard Stallman
2017-07-13 15:07         ` Jean Louis
2017-07-10  9:29       ` Richard Stallman
2017-07-09  0:39     ` Dmitry Gutov
2017-07-10  2:07       ` Chad Brown
2017-07-10  9:27       ` Richard Stallman
2017-07-10 13:02         ` Dmitry Gutov
2017-07-11 11:45           ` Richard Stallman
2017-07-11 15:00             ` Yuri Khan
2017-07-11 18:01               ` John Wiegley
2017-07-11 18:37                 ` Yuri Khan
2017-07-11 22:57               ` Richard Stallman
2017-07-12  7:56                 ` Yuri Khan
2017-07-12 16:12                   ` Richard Stallman
2017-07-12 17:49                     ` emacs.org website [was Re: Adding advisory notification for non-ELPA package.el downloads] Glenn Morris
2017-07-13 12:23                       ` Richard Stallman
2017-07-15  5:55                         ` John Wiegley
2017-07-12 16:35                   ` Glenn Morris
2017-07-11 22:57               ` Adding advisory notification for non-ELPA package.el downloads Richard Stallman
2017-07-12 23:12                 ` Nicolas Petton
2017-07-13 12:26                   ` Richard Stallman
2017-07-13 19:12                     ` Nicolas Petton
2017-07-15  1:33                       ` Richard Stallman
2017-07-17  8:16                         ` Nicolas Petton
2017-07-24  2:54                           ` Richard Stallman
2017-07-10 15:36         ` Ken Manheimer
2017-07-10 23:32           ` Richard Stallman
2017-07-08 14:57 ` Clément Pit-Claudel
2017-07-09  3:04   ` Yann Hodique
2017-07-10  9:29     ` Richard Stallman
2017-07-10 15:41       ` Ken Manheimer
2017-07-10 23:30         ` Richard Stallman
2017-07-10 16:48       ` Yann Hodique
2017-07-10 20:43   ` Joost Kremers
2017-07-11 22:57     ` Richard Stallman
2017-07-12  0:40       ` Stefan Monnier
2017-07-12 16:13         ` Richard Stallman
2017-07-11 16:04   ` Improving GNU ELPA (was: Adding advisory notification for non-ELPA package.el downloads) Stefan Monnier
2017-07-12  1:26     ` Improving GNU ELPA Clément Pit-Claudel
2017-07-12  2:19       ` Stefan Monnier
2017-07-12 23:17         ` Nicolas Petton
2017-07-13  2:03           ` Stefan Monnier
2017-07-13  2:07             ` Stefan Monnier
2017-07-13 19:18         ` Etienne Prud’homme
2017-07-13 22:07           ` Phillip Lord
2017-07-16 16:04     ` Improving GNU ELPA (was: Adding advisory notification for non-ELPA package.el downloads) Jonas Bernoulli
2017-07-16 17:11       ` Improving GNU ELPA Stefan Monnier
2017-07-16 17:28         ` Jonas Bernoulli
2017-07-17 16:46           ` Phillip Lord
2017-07-17 18:26           ` Stefan Monnier
2017-07-17 21:04             ` Richard Stallman
2017-07-17 21:21               ` Stefan Monnier
2017-07-18 10:08                 ` Phillip Lord
2017-07-18 13:35                   ` Stefan Monnier
2017-07-18 16:17                     ` Phillip Lord [this message]
2017-07-18 14:18                   ` Richard Stallman
2017-07-18 16:23                     ` Phillip Lord
2017-07-19  3:31                       ` Richard Stallman
2017-07-19 22:54                         ` Phillip Lord
2017-07-18 14:16                 ` Richard Stallman
2017-07-18 14:39                   ` Stefan Monnier
2017-07-18 16:20                     ` Phillip Lord
2017-07-18 17:26                       ` Stefan Monnier
2017-07-19 22:59                         ` Phillip Lord
2017-07-24  2:54                           ` Richard Stallman
2017-07-24 12:26                             ` Phillip Lord

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=87y3rloh35.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --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 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.