search for: submodules

...; > script/plugin install doesn''t support getting a specific version from > git yet. To do that you have to use ''git clone'' and then ''git checkout > 1.1.4'' (in this case). > As an alternative to script/plugin or git-clone, you can employ git-submodules (on GiT v1.5.3 or later) to obtain the effect of subversion externals. For example: ---> $ git-submodule add \ git://github.com/dchelimsky/rspec.git \ vendor/plugins/rspec Initialized empty Git repository in /home/byrnejb/projects/proforma.git/vendor/plugins/rspec/.git/ remote: Count...

2015-09-15 13:57 UTC+02:00, Patrick Masotta <masottaus at yahoo.com>: >>>> > > What's the default strategy for checking out new gnu-efi sources? > > We should have a way to set the version we want to work with > > and only update when we want to do so. > > That's true. All I did in these patches was to inline those shell > scripts in the

On mageia I'm using the following patch https://svnweb.mageia.org/packages/cauldron/syslinux/current/SOURCES/syslinux-nogit.patch?revision=600959&view=markup If it does solve your issue to, I could try pushing it into the repo. 2015-09-16 8:44 GMT+02:00 Thomas Letan via Syslinux <syslinux at zytor.com>: > Hi. > > Sometimes, it may happen that we do not want to clone a

I have a sub-application project that I had previously converted to edge rails under svn. Originally, vendor/rails was set up with svn:externals so that an svn update at the project''s root would pull the latest trunk along with all the other updates. Since Rails has moved to GiT and depreciated svn I decided to remove the svn:externals reference for vendor/rails and reinstall trunk using

...(loaded as svn_external or git submodule) We could load the plugins the same way as before ruby script/plugin install http://rspec.rubyforge.org/svn/trunk/rspec_core ruby script/plugin install http://rspec.rubyforge.org/svn/trunk/rspec_on_rails but it would be easier to install from git using git submodules using git and calling from RAILS_ROOT git submodule add git//github.com/dchelimsky/rspec_on_rails.git vendor/plugins/rspec_on_rails git submodule add git//github.com/dchelimsky/rspec_core.git vendor/plugins/rspec -------------- next part -------------- An HTML attachment was scrubbed... URL: htt...

...VM subproject you work on. Suppose also that you have an "umbrella" repository that holds submodule references to all those local mirrors. Various commits in the umbrella update submodule references: * Update llvm submodule to V * Update clang submodule to G * Don't update any submodules, fix scripts or something * Update compiler-rt submodule to Z | zip-downstream-fork.py will take these submodule updates and "inline" them into the umbrella history, making it appear that the downstream commits were applied against the monorepo in the order implied by the umbrella hi...

2015-09-14 14:15 UTC+02:00, Patrick Masotta <masottaus at yahoo.com>: >>>> > These few patches contain a few improvement about the > Makefiles for EFI. Mainly, to rebuild the files when needed, and only when > needed. The three shell scripts efi/{check,build,clean}-gnu-efi.sh > disappeared and > are now integrated as makefile recipes. > <<< >

Hey all, If you''re like me and use git submodules heavily (I vendor everything, and every plugin is a submodule), you might like to hear about code published this morning to make it easier to manage multiple git submodules in a shared-server environment. It''s imaginatively titled ''git-rake'', and it does Good Things like...

...we also get the UL0 commit > as predecessor to DL1. To be clear, is DC1 a commit that updates the clang submodule to UC1 and DL1 a separate local commit to llvm that merges in UL1? When zip-downstream-fork.py runs, it *always* uses the exact trees in use by each downstream commit, whether from submodules or the umbrella itself. It tries very hard to maintain the state of the trees as they appeared in the umbrella repository. Since in your case llvm isn't a submodule (it's the "umbrella"), DL1 will absolutely have the tree from UL1, not UL0. This is how migrate-downstream-fork.p...

I think it is erroneous to have the subrepository projects and tools listed in .gitignore. Instead of being ignored, methinks they should be listed as submodules in .gitmodules: [submodule "tools/clang"] path = tools/clang url = ../clang.git [submodule "projects/compiler-rt"] path = projects/compiler-rt url = ../compiler-rt.git [submodule "projects/test-suite"] path = projects/test-suite...

Hi Mehdi, I really like your idea of having a few "projected" git repositories (i.e. capture all commits that touch llvm/ into llvm.git, all that touch clang/ to clang.git etc.). I think it should solve our problem of llvm-forks-with-downstream changes very nicely (I think we won't have to do anything, as you said). I still want to sleep on it to see if I can spot any issues.

> On Jun 2, 2016, at 11:22 AM, dag at cray.com wrote: > > Matthias Braun via cfe-dev <cfe-dev at lists.llvm.org> writes: > >> 3. Make sure we have ala llvm-project-submodules setup in the official >> account. (Optional or necessary for the buildbots?) > >> 7. Make sure bisecting with llvm-project-submodules is a good experience > > I would like to have a fuller discussion about how to handle the > multiple repositories before going forward. Su...

...s to those files, but the commit message would be maintained and might therefore be confusing in the context of the individual repository, especially if only a small part of the commit affects that individual sub-repo. > > Essentially if the projects are supposed to be separate modules, then submodules is the solution to enforce that independence, ensuring commits in each module only affect that module and have appropriate commit messages for that context. > > If the submodules are in practice more intertwined then that then it does feel like an ideologically pure solution that in the end...

...fae8 100644 --- a/Build.PL +++ b/Build.PL @@ -150,22 +150,8 @@ sub ACTION_changelog return 1; } - # Check that git is available - eval "use Git;"; - if($@) { - $self->log_info("Git is not installed\n"); - return 1; - } - - # Update submodules to get git2cl - my $repo = Git->repository(Directory => '.'); - - eval { - $repo->command_noisy('submodule', 'update'); - }; - - if($@) { - $self->log_info("Failed to initialise git2cl\n"); + unless(system("git", &...

He all, I've updated the downstream fork zipping tool that I posted about last November [1]. It is much improved in every way. The most important enhancements are: - Does a better job of simplifying history - Handles nested submodules - Will put non-submodule-update content in a subdirectory of the monorepo - Updates tags In addition there are plenty of the requisite bug fixes. The latest version of the tool can be found here: https://github.com/greened/llvm-git-migration/tree/zip With the nested submodules and the subdi...

...t; recently). > > svn-bisect is a trival tool and should be part of every good svn > installation. While I never got around to script the part of "update all > subrepos to the same revision", it certainly doesn't involve any > addition checks. From what I can tell, git submodules don't even support > that easily. I might be wrong though. In a nutshell: git-submodules basically records a git revision of your submodules with the commits. You can make such revision switches a natural part of commits. "git submodule update [--recursive]" will bring your submod...

It has also submodules. https://github.com/llvm-project/llvm-project-submodule Both llvm-project(-tree) and (-submodule) have refs/notes/commits. On Tue, Jun 28, 2016 at 1:13 AM Renato Golin via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On 27 June 2016 at 17:03, Rafael Espíndola <rafael.espindola at...

...9;git://git.code.sf.net/p/gnu-efi/code' into submodule path 'gnu-efi' failed As a workaround, I set up a git proxy with socat as described on https://gist.github.com/sit/49288 (which is generally useful). The syslinux wiki could point to that... but is there a direct way to get the submodules to use http? --- Robert Elliott, HPE Persistent Memory

Hi. Sometimes, it may happen that we do not want to clone a repo (here the submodule) and just use the version installed in the system. I have myself one use case. Unfortunately, it is not possible to do that with syslinux AFAIK Thomas Le 15/09/2015 19:52, Celelibi via Syslinux a ?crit : > 2015-09-15 13:57 UTC+02:00, Patrick Masotta <masottaus at yahoo.com>: >>>>>

Björn Pettersson A <bjorn.a.pettersson at ericsson.com> writes: > In llvm (split) we have: > > UL4->UL3->UL2->UL1->UL0 > \ > ...->DL2->DL1 > > In clang (split) we have: > > UC4->UC3->UC2->UC1->UC0 > \ > ...->DC2->DC1 > > > DL1 is a commit that updates the