Submodule update with make about data-driven-dynamics HOT 4 CLOSED

git submodule update --init --recursive just seems to always check out the latest commit specified in the submodule.

While git submodule update --remote --merge updates the commit of the submodule to the latest stage.

So we should maybe just adapt it to the latter?

Yes please!

from data-driven-dynamics.

@manumerous Lets not mix PRs with different features. This change is not related to tiltrotors therefore doesn't belong to #70

I have no objections, but the make submodulesupdate comes from PX4 repos that share this.

My main intention with these make targets are to use the autocomplete with tabs, so as long as this works that is fine for me.

from data-driven-dynamics.

Sorry i need to correct my self.

git submodule update --init --recursive just seems to always check out the latest commit specified in the submodule.

While git submodule update --remote --merge updates the commit of the submodule to the latest stage.

So we should maybe just adapt it to the latter?

from data-driven-dynamics.

@manumerous Lets not mix PRs with different features. This change is not related to tiltrotors therefore doesn't belong to #70

Thats also okay for me. It was just something I needed to do to continue my work on that branch. But I can do it manually until the branch is merged.

I have no objections, but the make submodulesupdate comes from PX4 repos that share this.

Okay we can keep this for consistency.

My main intention with these make targets are to use the autocomplete with tabs, so as long as this works that is fine for me.

from data-driven-dynamics.