[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Improving GNU ELPA

From: Phillip Lord
Subject: Re: Improving GNU ELPA
Date: Tue, 18 Jul 2017 17:17:02 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2.50 (gnu/linux)

Stefan Monnier <address@hidden> 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

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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]