In our move to Gitlab, we can do better.
Given Gitlab emails contain even less information and context than
Phabricator which themselves contained even less information and
context
than Reviewboard back then, I don't see how this will change or
improve
anything.
Thanks for the feedback
What would be involved in moving kdiff3 to gitlab?
I would like someone to audit the way kdiff3 uses KIO on remote files.
Specifically I am looking for anyway error/completion signals can be missed
causing an indefinite hang until the compare is canceled. Also any extra
work being done by kdiff3 that should be handed off to KIO. There should
also
On 7/2/19 3:53 PM, Valorie Zimmerman wrote:
Please lets keep in mind that this is not a thread to complain about
Gitlab. No platform is perfect, and we're not yet on production machines.
This thread is about how to make our review process great for both
newbies and experienced developers,
