Re: [boost] [git] How the blazes are you supposed to update all the submodules?

Subject: Re: [boost] [git] How the blazes are you supposed to update all the submodules?
From: Cox, Michael (mhcox_at_[hidden])
Date: 2013-12-19 19:39:40

On Thu, Dec 19, 2013 at 7:25 AM, Daniel James <daniel_at_[hidden]>wrote:

> On 19 December 2013 14:11, Sergey Cheban <s.cheban_at_[hidden]> wrote:
> > On 19.12.2013 17:32, Daniel James wrote:
> >
> >>> When you pull the superproject, it only checks out the submodules at
> >>> the specific revision that, I believe, is updated manually now by
> >>> someone with the write access to the superproject.
> >>
> >> I have a script which updates it, but I'm running it manually as it's
> >> not quite ready to be a cron job. If it's not too much for the server
> >> it should be updating automatically soon.
> >
> > May be, it is better to use github's service hooks instead of cron to
> > initiate the update?
> >
> > https://help.github.com/articles/post-receive-hooks
>
> Maybe, but it would introduce concurrency issues (if two modules are
> pushed to in quick succession). If I get it working in a cron job, I
> can think about hooks later. FWIW I am using a hook to update the
> website.
>

Once you have more than one git repository (superproject and submodules),
by definition, you *will* have concurrency issues no matter how you do it.
 It's just the size of the window of vulnerability you can try to minimize.

Michael