search for: submodul

...; > 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: Cou...

...egy 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 Makefiles, including the 'git submodule update --init'. > So I didn't change any behavior in that regard. When you make directly > or indirectly the targets efi32 or efi64, the submodule is checked out > at the revision registered for the current syslinux commit. > > Currently, if you want to checkout another...

...nux-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 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 <m...

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

This is a request to split up the repository into at least two repositories rspec rspec_core (loaded as svn_external or git submodule) rspec_on_rails (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 insta...

Building on the great work that James Knight did on migrate-downstream-fork.py (Thanks, James!) [1], I've created a simple tool to take migrated downstream fork branches and zip them into a single history given a history containing submodule updates of subprojects [2]. With migrate-downstream-fork.py, one is left with a set of unrelated histories, one per subproject: llvm clang compiler-rt * V Add my fancy LLVM feature * G Fix my dumb clang bug * Z Merge from upstream compiler-r...

...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 Makefiles, including the 'git submodule update --init'. So I didn't change any behavior in that regard. When you make directly or indirectly the targets efi32 or efi64, the submodule is checked out at the revision registered for the current syslinux commit. Currently, if you want to checkout another revision of the submodule, y...

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 li...

...2->UL3->UL2->UL1->UL0->UC1 > > Our DL1 commit should preferably have UL1 as parent after > conversion > > UL4->UC2->UL3->UL2->UL1->UL0->UC1 > | > ...->DL1 > > but since it also includes DC1 (via submodule reference) we > want to zip in DC1 before DL1, right? > > UL4->UC2->UL3->UL2->UL1->UL0->UC1 > | > ...->DC1->DL1 > > The problem is that DC1 is based on UC1, so we would get something > like this > > UL4-&...

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-sui...

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....

...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 en...

The changelog action needs to checkout git2cl as a submodule. For some reason, when called through the Git module, command('submodule', 'update') was doing something unfathomable, and different to just calling 'git submodule update'. As Git is just a command line wrapper anyway, I've sidestepped this by just calling the command d...

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 sub...

...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 subm...

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 a...

The wiki: http://www.zytor.com/mailman/listinfo/syslinux says to use this to clone git with http rather than git protocol: git clone --recursive http://repo.or.cz/syslinux.git a-new-directory That works for the main project, but fails for the gnu-efi submodule, which specifies the git protocol in its .config file: $ git clone --recursive http://repo.or.cz/syslinux.git syslinux Cloning into 'syslinux'... remote: Counting objects: 50634, done. remote: Total 50634 (delta 0), reused 0 (delta 0) Receiving objects: 100% (50634/50634), 22.12 MiB...

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>: >>&g...

...gt; 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 clang submodule to DC1 (and in this > scenario at the same time merges UL1 and DL2 in llvm). Ok, in that case I would expect the resulting history to look like this: UL4->UC2->UL3->UL2->UL1->UL0->UC1 <- monorepo/master | \ \...