-
Notifications
You must be signed in to change notification settings - Fork 866
New issue
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
Filestorage roadmap milestone #1204
Conversation
Signed-off-by: deadprogram <ron@hybridgroup.com>
Signed-off-by: deadprogram <ron@hybridgroup.com>
…t results on macOS. See https://forum.opencv.org/t/match-template-different-results-on-mac-m1/10026 and other similar issues. Signed-off-by: deadprogram <ron@hybridgroup.com>
Hello @diegohce Thank you very much for working on this set of features! I notice that this PR seems to have picked up bunch of commits that are in the One way to address this might be to create a new branch from What do you think? |
Hi Ron.
Don't know how to do that. I understand that commit messages got dirty but
is it necessary to do that?
…On Sat, Aug 24, 2024 at 6:02 AM Ron Evans ***@***.***> wrote:
Hello @diegohce <https://github.com/diegohce>
Thank you very much for working on this set of features!
I notice that this PR seems to have picked up bunch of commits that are in
the dev branch. Perhaps you should have started with the latest dev
branch?
One way to address this might be to create a new branch from dev, then git
cherry-pick the specific commits for filestorage into that branch, and
open a new PR from that branch to dev.
What do you think?
—
Reply to this email directly, view it on GitHub
<#1204 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADJCC6CFBGSVTJDLNRZEKT3ZTBDY7AVCNFSM6AAAAABNAYMNPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBYGIZTENBSGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Yes, because we need to keep the commit log clean. You might be better off just creating a new PR based on |
ok
…On Mon, Aug 26, 2024 at 4:59 AM Ron Evans ***@***.***> wrote:
is it necessary to do that?
Yes, because we need to keep the commit log clean. You might be better off
just creating a new PR based on dev and manually adding the new files in
a single new commit.
—
Reply to this email directly, view it on GitHub
<#1204 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADJCC6C4JVUM3ZVOIDNKNI3ZTLN7PAVCNFSM6AAAAABNAYMNPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBZGU4DQMRRGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
done. checks are running as I write this..
…On Mon, Aug 26, 2024 at 11:56 PM Diego Cena ***@***.***> wrote:
ok
On Mon, Aug 26, 2024 at 4:59 AM Ron Evans ***@***.***>
wrote:
> is it necessary to do that?
>
> Yes, because we need to keep the commit log clean. You might be better
> off just creating a new PR based on dev and manually adding the new
> files in a single new commit.
>
> —
> Reply to this email directly, view it on GitHub
> <#1204 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ADJCC6C4JVUM3ZVOIDNKNI3ZTLN7PAVCNFSM6AAAAABNAYMNPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBZGU4DQMRRGU>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
Filestorage roadmap milestone