Jaseem Abid via llvm-dev
2018-May-10 05:07 UTC
[llvm-dev] Migrating the llvm-emacs mode to a separate git repository
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. 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 -- Regards, Jaseem Abid https://twitter.com/jaseemabid
Tim Northover via llvm-dev
2018-May-10 08:51 UTC
[llvm-dev] Migrating the llvm-emacs mode to a separate git repository
On 10 May 2018 at 06:07, Jaseem Abid via llvm-dev <llvm-dev at lists.llvm.org> wrote:> 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.Wouldn't svn be better here? It ought to allow you to checkout just the utils/emacs directory (or not even that with "svn cat"). We're eventually planning to move to git as the primary source of truth, but there will always be svn fallbacks in place.> 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.That's a separate issue, of course. I'm not entirely convinced there are hordes of Emacs developers just itching to help out with tablegen-mode but deterred by the big repository. But maybe I'm wrong. Cheers. Tim.
Anton Korobeynikov via llvm-dev
2018-May-10 09:14 UTC
[llvm-dev] Migrating the llvm-emacs mode to a separate git repository
As far as I can see, melpa dropped svn support some time ago.... https://github.com/melpa/melpa/pull/4802 On Thu, May 10, 2018 at 11:51 AM, Tim Northover via llvm-dev <llvm-dev at lists.llvm.org> wrote:> On 10 May 2018 at 06:07, Jaseem Abid via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> 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. > > Wouldn't svn be better here? It ought to allow you to checkout just > the utils/emacs directory (or not even that with "svn cat"). We're > eventually planning to move to git as the primary source of truth, but > there will always be svn fallbacks in place. > >> 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. > > That's a separate issue, of course. I'm not entirely convinced there > are hordes of Emacs developers just itching to help out with > tablegen-mode but deterred by the big repository. But maybe I'm wrong. > > Cheers. > > Tim. > _______________________________________________ > 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
Justin Bogner via llvm-dev
2018-May-10 22:18 UTC
[llvm-dev] Migrating the llvm-emacs mode to a separate git repository
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
Anton Korobeynikov via llvm-dev
2018-May-10 22:56 UTC
[llvm-dev] 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
Maybe Matching Threads
- Migrating the llvm-emacs mode to a separate git repository
- Migrating the llvm-emacs mode to a separate git repository
- Migrating the llvm-emacs mode to a separate git repository
- Migrating the llvm-emacs mode to a separate git repository
- Migrating the llvm-emacs mode to a separate git repository