Investigate and port TET matching rules filter tests(cert)
Relates: https://pagure.io/389-ds-base/issue/48851
Author: aborah
Reviewed by: ???
rebased onto 4f592c2774f9391fe667e05d5fa0f94e4055047d
I saw the discussion on the mail list. So what is an update for this?
rebased onto bc1c4be0153687c7961a7d788eee893d3b6f5dac
@spichugi ready to review
Please, describe the resolution for the mail list discussion. What was the final agreement there? I think it is important to have an overview and the explanation here. Please, don't ignore the questions...
rebased onto 09ece9834f4e23736210010262d342a68dce7c53
Resolution is done by @vashirov in the issue . Please take a look .
PR is ready to review.
In which issue? The one linked in the description is 3 years old and contains only a bunch of commit hashes listed. How am I supposed to find out what's going on? Simon was asking you for a summary, even a link would work better...
Also, again, you still keep rebasing which makes tracking changes very hard to follow. And there is no way to back-track what was the original commit. At least describe in the comments what changed with a rebase.
Resolution is done by @vashirov in the issue . Please take a look . In which issue? The one linked in the description is 3 years old and contains only a bunch of commit hashes listed. How am I supposed to find out what's going on? Simon was asking you for a summary, even a link would work better... Also, again, you still keep rebasing which makes tracking changes very hard to follow. And there is no way to back-track what was the original commit. At least describe in the comments what changed with a rebase.
In which issue? The one linked in the description is 3 years old and contains only a bunch of commit hashes listed. How am I supposed to find out what's going on? Simon was asking you for a summary, even a link would work better... Also, again, you still keep rebasing which makes tracking changes very hard to follow. And there is no way to back-track what was the original commit. At least describe in the comments what changed with a rebase.
Issue : https://pagure.io/389-ds-base/issue/50443 PR: https://pagure.io/389-ds-base/pull-request/50466
rebased onto 51f8169bcf6891c9acd1d2e02222638d63b7b07c
rebased onto f4af5f1a960058b2800e188699d1de74408cee36
rebased onto 1423411e054a79e4a34ccf964912e0e253be6a58
rebased onto 717194bdb65410ce70bf78453315206d132b7bd0
Pull-Request has been closed by aborah
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This pull request has been cloned to Github as issue and is available here: - https://github.com/389ds/389-ds-base/issues/3492
If you want to continue to work on the PR, please navigate to the github issue, download the patch from the attachments and file a new pull request.
Thank you for understanding. We apologize for all inconvenience.
Pull-Request has been closed by spichugi
Investigate and port TET matching rules filter tests(cert)
Relates: https://pagure.io/389-ds-base/issue/48851
Author: aborah
Reviewed by: ???