We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The text was updated successfully, but these errors were encountered:
@arpansur @da-gazzi we can move the technical discussion here maybe... and link any PR e.g., in HCI for the multi-initiatior arbiter.
Sorry, something went wrong.
Also.. @adimauro-iis if an issue actually involves more than one repo, do we capture that here?
Good point, I like a lot the idea of associating an issues to specific code changes into a repo.
I think that whenever an issue requires changes into another repo we could:
Let's pretend this issue Produce a "nice" error when interfaces are improperly parametrized hci#42 is needed for our feature to be added
Option 2 tracks everything but require more diligence...I am fine with both
FrancescoConti
arpansur
No branches or pull requests
The text was updated successfully, but these errors were encountered: