Tom Honermann via llvm-dev
2016-Jun-29 15:50 UTC
[llvm-dev] [cfe-dev] Git Move: GitHub+modules proposal
On 6/29/2016 10:03 AM, Renato Golin via cfe-dev wrote:> Since the umbrella project cannot see the sub-modules' commits without > some form of update, there are two ways to do this: > > P. Per push: Every push (not commit) on all other repositories will > trigger a hook that will hit a URL on our server, telling it to > generate an incremental ID, update some umbrella's SeqID property (or > even a commit SHA) and update the sub-modules.How would you coordinate dependent updates to the sub-modules? For example, in the case where someone makes a change to the LLVM sub-module that requires changes to the Clang sub-module? Would there be some way for a developer to push both sets of updates as an atomic update to the umbrella project? It probably doesn't matter often, as long as the updates to both sub-modules are pushed close together in time. Tom.
Renato Golin via llvm-dev
2016-Jun-29 19:00 UTC
[llvm-dev] [cfe-dev] Git Move: GitHub+modules proposal
On 29 June 2016 at 16:50, Tom Honermann <Thomas.Honermann at synopsys.com> wrote:> How would you coordinate dependent updates to the sub-modules?We won't. Not now. Maybe later. Right now, doing that means changing how we work and we're trying to make the least number of changes at a time. But this is the most requested feature and I'm sure we'll find something that will work as soon as everything is stable. cheers, --renato
Craig, Ben via llvm-dev
2016-Jun-29 19:05 UTC
[llvm-dev] [cfe-dev] Git Move: GitHub+modules proposal
On 6/29/2016 2:00 PM, Renato Golin via llvm-dev wrote:> On 29 June 2016 at 16:50, Tom Honermann <Thomas.Honermann at synopsys.com> wrote: >> How would you coordinate dependent updates to the sub-modules? > We won't. Not now. Maybe later. > > Right now, doing that means changing how we work and we're trying to > make the least number of changes at a time. > > But this is the most requested feature and I'm sure we'll find > something that will work as soon as everything is stable.If I understand the proposal and the status quo correctly, the migration to Git won't make cross-repo updates any worse than it is currently. I think that avoiding regressions is an excellent goal for the initial migration. -- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project