URL: https://github.com/SSSD/sssd/pull/543
Title: #543: SYSDB: When marking an entry as expired, also set the
originalModifyTimestamp to 1
fidencio commented:
"""
Ack, thanks for the change!
"""
See the full comment at
https://github.com/SSSD/sssd/pull/543#issuecomment-378245994
URL: https://github.com/SSSD/sssd/pull/543
Title: #543: SYSDB: When marking an entry as expired, also set the
originalModifyTimestamp to 1
jhrozek commented:
"""
CI: http://vm-031.$ABC/logs/job/87/50/summary.html
"""
See the full comment at
URL: https://github.com/SSSD/sssd/pull/543
Title: #543: SYSDB: When marking an entry as expired, also set the
originalModifyTimestamp to 1
jhrozek commented:
"""
Thanks for fixing the pep8 issue. I pushed the patches to our internal CI and
Coverity.
"""
See the full comment at
URL: https://github.com/SSSD/sssd/pull/543
Title: #543: SYSDB: When marking an entry as expired, also set the
originalModifyTimestamp to 1
fidencio commented:
"""
@jhrozek, I've made the change and mistakenly pushed to your branch (well, not
so bad in the end as it may save you some time).
URL: https://github.com/SSSD/sssd/pull/543
Title: #543: SYSDB: When marking an entry as expired, also set the
originalModifyTimestamp to 1
fidencio commented:
"""
@jhrozek, please, just squash the following patch into your:
```
[ffidenci@pessoa sssd]$ cat
URL: https://github.com/SSSD/sssd/pull/543
Title: #543: SYSDB: When marking an entry as expired, also set the
originalModifyTimestamp to 1
fidencio commented:
"""
@jhrozek, CentOS CI failed due to pep8 issues.
"""
See the full comment at
