[PATCH 1/2] Inverted steps in update_lock_info_context_step

Aleksander Morgado aleksander at aleksander.es
Thu Jun 30 14:16:43 UTC 2016

On Wed, Jun 1, 2016 at 6:16 PM, Dan Williams <dcbw at redhat.com> wrote:
> On Wed, 2016-06-01 at 16:48 +0200, Aleksander Morgado wrote:
>> On Wed, Jun 1, 2016 at 4:34 PM, Carlo Lobrano <c.lobrano at gmail.com>
>> wrote:
>> >
>> > Hi, has this change already merged?
>> Not yet; IIRC Dan suggested to merge it after releasing 1.6.0.
> Yeah, I did suggest that, because I thought it was quite a large
> (though probably correct!) change in behavior right before a release
> and we have no idea how modems will react to it.  It also affects *all*
>  modems since it's not limited to one plugin...  I'm willing to be
> convinced otherwise, but I'm wary of changes to a huge class of devices
> so close to a release.

I wouldn't want to lose track of this change, so I'm tempted to just
branch git master into a 1.6 specific branch, waiting to finish the
qmi-over-mbim thing, and keep on working and pushing changes to git


More information about the ModemManager-devel mailing list