Re: Improving GNU ELPA

[Phillip Lord]

Stefan Monnier <address@hidden> writes:

>>> There are no real rules, here, other than the fact that elpa.git may be
>>> modified by us directly, so if the maintainer decides to keep the
>>> "upstream" elsewhere it's his responsibility to deal with the fallout
>> This bit I don't like!
>
> You're not alone, so in general we should try to avoid it.
>
>> What sort of commits do you do locally?
>
> Not sure what you mean by "locally".  Do you mean, what kinds of commits
> do we want to install directly into elpa.git (for those cases where the
> upstream is elsewhere)?

Yes, precisely so.

> Typically things like incorrect copyright notices or compilation breakage.

Does ELPA not check for the copyright? I.e. if it's incorrect, it will
be wrong in the git repo only and not in the distributed ELPA package.


>> Would scripting something to branch, and do git-request-pull to the
>> upstream be a substitute?
>
> Nowadays, most of time I send a patch via email to the maintainer rather
> than committing directly.  It's more tedious but since I now do much less
> janitorial work on elpa.git code it's OK.

janitorial work is always tedious!

Phil