llvm dev - May 2018 - Migrating the llvm-emacs mode to a separate git repository

Another crazy idea – can mepla use shallow clone / sparse checkout?
Will it speed up all the things?

On Fri, May 11, 2018 at 1:18 AM, Justin Bogner via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> Jaseem Abid via llvm-dev <llvm-dev at lists.llvm.org> writes:
>> Hello llvm devs,
>>
>> Melpa[1] is pretty much the most common package manager for emacs and
very
>> recently the llvm-mode got removed from it[2] due to performance
issues.
>> This issue is not unique to llvm-mode, but affects a bunch of projects
with
>> very large git repositories[3].
>>
>> Will it be possible to split this into a new separate git repo? This
should
>> make it easier for the emacs community to work with this code and make
it
>> less intimidating for new users to contribute to.
>
> I don't think splitting these out of the main llvm repo would make
sense
> given that we're probably headed to having fewer repositories in the
> future. Besides which, it's pretty convenient to have these within the
> llvm source.
>
> As for melpa, I think mirroring utils/emacs to a dedicated repo seems
> fine. You could presumably use git subtree merges and make a read-only
> mirror that would be perfectly useable.
>
>> Current melpa maintainers and previous llvm-mode commitors are in CC.
>>
>> [1] https://melpa.org
>> [2]
>>
https://github.com/melpa/melpa/commit/aa2d7a88731ecd9410ab7dc887a7a5f837d8a93b
>> [3] https://github.com/melpa/melpa/issues/5361#issuecomment-387710812
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev


-- 
With best regards, Anton Korobeynikov
Department of Statistical Modelling, Saint Petersburg State University

On 10 May 2018 at 23:56, Anton Korobeynikov via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> Another crazy idea – can mepla use shallow clone / sparse checkout?
> Will it speed up all the things?
Even http would do, the raw file links on github are pretty stable.

Tim.

Another idea: extract the history of tablegen-mode into a separate orphan
branch, and merge it routinely. Have a policy of always using that branch
to contribute to tablegen-mode, and merge it back into mainline routinely.
MELPA can then request git to do a single-branch clone.

Ram
On Thu, May 10, 2018 at 11:57 PM Tim Northover <t.p.northover at
gmail.com>
wrote:
> On 10 May 2018 at 23:56, Anton Korobeynikov via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
> > Another crazy idea – can mepla use shallow clone / sparse checkout?
> > Will it speed up all the things?
>
> Even http would do, the raw file links on github are pretty stable.
>
> Tim.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20180511/8156da36/attachment.html>