Conversation
|
Please reference the original bug report (issues#26661) in PR to help the reviewer quickly locate and reproduce the issue. Additionally, I believe using ternary expression is better than nested if-else loops in this case. |
|
sure , i'll try to modify it using ternary operator |
|
I've updated the code to use the ternary operator as suggested. Let me know if further changes are needed! |
|
Have you read https://github.com/opencv/opencv/wiki/How_to_contribute#making-a-good-pull-request ?
That is, if you add fixup commits to your pull request, you should typically squash them using |
|
Thank you for your feedback . I have read the guidelines on making-a-good-pull-request , and also i squashed the fixup commits directly into the original commit using git rebase -i . |
You need to exclude unrelated files from PR |
|
i have excluded the unrelated files from my pull request , please let me know if there are any further changes |
Wrong. excluded != deleted. Please learn git basics. PR should have 1 commits and 1 changes file. |
|
Sorry for the inconvenience caused by me . I'll correct my mistake and
ensure that it won't happen again and also Thank you for your guidance.
…On Wed, Dec 25, 2024 at 7:23 AM Alexander Alekhin ***@***.***> wrote:
i have excluded the unrelated files from my pull request , please let me
know if there are any further changes
Wrong.
excluded != deleted.
Please learn git basics.
PR should have 1 commits and 1 changes file.
—
Reply to this email directly, view it on GitHub
<#26662 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDO247IY4OGGWOVMV4UTBG32HIFZ3AVCNFSM6AAAAABUCTRKXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRRGUZTQNZRG4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
Once you have the commits all cleaned up, ping me and I can review. I know Cocoa. |
|
Thanks, I will!
…On Thu, Jan 9, 2025 at 4:50 AM Sean McBride ***@***.***> wrote:
Once you have the commits all cleaned up, ping me and I can review. I know
Cocoa.
—
Reply to this email directly, view it on GitHub
<#26662 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDO247LWIO3KMAO57T4TETL2JWXDXAVCNFSM6AAAAABUCTRKXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZYHA3DINJRG4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
@RoshniUG Friendly reminder. |
|
Yes, thanks for the reminder.
…On Fri, 24 Jan, 2025, 5:15 pm Alexander Smorkalov, ***@***.***> wrote:
@RoshniUG <https://github.com/RoshniUG> Friendly reminder.
—
Reply to this email directly, view it on GitHub
<#26662 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDO247KW4AU3MV5QMFW63UL2MIRVJAVCNFSM6AAAAABUCTRKXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJSGMZTEMRVGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@RoshniUG Friendly reminder. |
|
I made changes , Please look into it .
…On Fri, Jan 31, 2025 at 7:20 PM Alexander Smorkalov < ***@***.***> wrote:
@RoshniUG <https://github.com/RoshniUG> Friendly reminder.
—
Reply to this email directly, view it on GitHub
<#26662 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDO247JFOOYXPEORQ24PNCT2NN5SBAVCNFSM6AAAAABUCTRKXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRXGQYDCNJUHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@RoshniUG please fix CI warnings: |
|
Sure sir I'll look into it |
seanm
left a comment
There was a problem hiding this comment.
This lgtm conceptually.
The indentation seems messed up though.
|
@RoshniUG Friendly reminder on CI warnings. |
|
There is merge conflict still. |
Update window_cocoa.mm opencv#26662 ### Pull Request Readiness Checklist See details at https://github.com/opencv/opencv/wiki/How_to_contribute#making-a-good-pull-request - [x] I agree to contribute to the project under Apache 2 License. - [x] To the best of my knowledge, the proposed patch is not based on a code under GPL or another license that is incompatible with OpenCV - [x] The PR is proposed to the proper branch - [x] There is a reference to the original bug report and related work - [x] There is accuracy test, performance test and test data in opencv_extra repository, if applicable Patch to opencv_extra has the same branch name. - [x] The feature is well documented and sample code can be built with the project CMake - [x ] Added reference to the original bug report (opencv#26661). - [x]Updated the code as per the reviewer's suggestion to use a ternary operator. - [x] Verified that the feature is properly documented and can be built with CMake.
Pull Request Readiness Checklist
See details at https://github.com/opencv/opencv/wiki/How_to_contribute#making-a-good-pull-request
Patch to opencv_extra has the same branch name.