Re: [boost] git reset and force push

Subject: Re: [boost] git reset and force push
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2015-10-07 11:35:25

On 07.10.2015 18:26, Raffi Enficiaud wrote:
> Le 07/10/15 16:52, Andrey Semashev a écrit :
>>
>> The superproject is automatically updated to refer to the latest commits
>> in develop and master branches. I think it may skip a few pushed commits
>> if pushes are done in quick succession, but really, I don't care. For
>> all practical purposes you can assume that the superproject always
>> refers to the latest commit.
>
> You're counting on the fact that things get updated fast, etc etc.

I'm not. I don't use superproject references to commits.

> What
> counts is the "VC" part in DVCS: the revision of the superproject and
> the associated submodules. What you are doing does might lead to an
> inconsistent state (plus the fact that I do not see any added value in
> having the branches). But that is another topic.

If such inconsistent state is possible at a given point then you are not 
protected from it by using the superproject references to submodules. 
There's no consistency control in the superproject updates.