Boost - Dev mailing list wrote

On 8/4/17 05:44, Peter Dimov via Boost wrote:

...

Several submodules have different names on master and develop:

- compute (libs/compute on develop) - couroutine2 (libs/coroutine2 on develop) - dll (libs/dll on develop) - qvm (libs/qvm on develop) - vmd (libs/vmd on develop)

Should we normalize the names on develop?

I think that after fixing .gitmodules, these submodules will appear as-if deinitialized, and would need a `git submodule update --init` to reappear under the new names.

There are also libs/hana and libs/metaparse, which have consistent (although "wrong") names on both master and develop. Not sure if we need to bother with them.

I would prefer if we "fix" all of the names. Normalize those on develop and correct hana and metaparse.

+1 I think I copied Metaparse's pull request that added itself as a submodule, and this is why Hana ended up wrong as well. I see no reason to keep it the way it is today. I can submit a PR for Hana if you want, but I guess it's simple for you to just address all of those issues at once? Louis -- View this message in context: http://boost.2283326.n4.nabble.com/Submodule-name-mismatches-between-master-... Sent from the Boost - Dev mailing list archive at Nabble.com.

Oliver Kowalke wrote:

2017-08-04 14:44 GMT+02:00 Peter Dimov via Boost :

...

Several submodules have different names on master and develop: ... Should we normalize the names on develop? ...

What do I have to do as one of the maintainers in order to fix the issue?

Nothing, it's a superproject issue.

Boost - Dev mailing list wrote

On 4 August 2017 at 13:44, Peter Dimov via Boost <

boost@.boost

> wrote:

...

There are also libs/hana and libs/metaparse, which have consistent (although "wrong") names on both master and develop. Not sure if we need to bother with them.

I wouldn't bother. What the names are is mostly irrelevant, they're mainly used as internal identifiers. Having them change arbitrarily in the history is more likely to cause a problem than not following a naming convention. It's very easy for scripts to handle the names, and users aren't normally aware of them.

Not everything is about minimizing the risk for causing problems (especially when it's almost inexistent, like here). IMO, consistency is much more important, even if it's just for the sake of it because they're just internal names. I've asked Peter to change Hana and Metaparse as well on his PR: https://github.com/boostorg/boost/pull/158. Louis -- View this message in context: http://boost.2283326.n4.nabble.com/Submodule-name-mismatches-between-master-... Sent from the Boost - Dev mailing list archive at Nabble.com.