search for: eaf492b

...projects) would be simple decoupled, individual git repositories. You would be able to check them out however you want and commit to them individually. There would be an extra "integration repository" on top that would only provide the service that tells "r12345 is llvm:36c941c clang:eaf492b compiler-rt:6d77ea5". This repository should be managed transparently by some server-side integration. The provided scripting I was referring to would just be a convenience that is using this extra layer of metadata ("integration repository") to be able checkout the other individual...

...cts) would be simple decoupled, individual git repositories. You would be able to check them out however you want and commit to them individually. > There would be an extra "integration repository" on top that would only provide the service that tells "r12345 is llvm:36c941c clang:eaf492b compiler-rt:6d77ea5". This repository should be managed transparently by some server-side integration. This actually sounds like a really good idea even if a full move to git gets blocked for some reason. It seems like it could be a fairly common requirement: I don't suppose you know of a...

On 31 May 2016 at 21:28, Mehdi Amini <mehdi.amini at apple.com> wrote: > Ideally, I'd prefer the cross-repository to be handled with an extra layer, in a way similar as described in: https://gerrit-review.googlesource.com/Documentation/user-submodules.htm (somehow conceptually similar to Android manifests XML files). > It would be easy to have tooling/scripts for llvm that would

...al git repositories. You >> would be able to check them out however you want and commit to them >> individually. >> There would be an extra "integration repository" on top that would >> only provide the service that tells "r12345 is llvm:36c941c >> clang:eaf492b compiler-rt:6d77ea5". This repository should be managed >> transparently by some server-side integration. >> The provided scripting I was referring to would just be a convenience >> that is using this extra layer of metadata ("integration repository") >> to be...

...repositories. You would be able to check them out however you want >>> and commit to them individually. >>> There would be an extra "integration repository" on top that would >>> only provide the service that tells "r12345 is llvm:36c941c >>> clang:eaf492b compiler-rt:6d77ea5". This repository should be >>> managed transparently by some server-side integration. >> >> This actually sounds like a really good idea even if a full move to >> git gets blocked for some reason. It seems like it could be a fairly >> comm...

> On May 31, 2016, at 1:16 PM, Chris Lattner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > >> On May 31, 2016, at 12:31 PM, Renato Golin via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> There has been some discussion on IRC about SVN hosting and the perils >> of doing it ourselves. The consensus on the current discussion was >> that moving to a