Fix M_Oline.segment as discussed in #3826

[AHaumer]

Utilize Short with instance name M for backwards compatibility.
@dietmarw can you back-port this to maint/4.0.x (see #3818)?
I suppose after merging this PR and #3828 we should rebase #3819 or create a new PR.

[dietmarw]

Just to explain (again) the change of milestone here: master is the next MINOR (or MAJOR). Any bugfix changes here will get backported to maint/4.0.x and need a separate PR once this one is merged.

[dietmarw]

Looks good.

[AHaumer]

Just to explain (again) the change of milestone here: master is the next MINOR (or MAJOR). Any bugfix changes here will get backported to maint/4.0.x and need a separate PR once this one is merged.

Ok so no backport to 3.2.3?
Are you going to take care of backport to maint/4.0.x?

[dietmarw]

Ok so no backport to 3.2.3?

Not unless you do that manually. I have no interest and don't see the point of backporting this to 3.2.3. I would do it if it was a simple pick of the commits. But that is not possible since the file structure has changed quite a lot since then.

Are you going to take care of backport to maint/4.0.x?

Yes, already done. I just wait with the PR until this got successfully merged.

[AHaumer]

To be honest: I'd drop the back-port to 3.2.3 - @ditmarw what's your opinion?
It seems that @max-privato was the first user to complain about the Lines models, and a lot more issues came up when taking care of that (see #3828 and missing examples).

[dietmarw]

That's fine with me. I don't think it is a huge issue and as you said, this was the very first time it was raised. So I doubt that user models exist that are impacted by this. Any new users will most likely start with MSL 4.0.0 anyway where the bugfix will be available at some point.

[christiankral]

The code looks good