On Tue, 20 Sep 2022 08:03:21 -0400 "Bruce Ashfield" <[email protected]> wrote:
> The patch itself looks fine, the only issue for easy processing is > that it is attached to email, versus being the email. If you send the > patch with git-send-email, it will take care of those details. I never used git-send-email - didn't know it - and I don't know if I like it because of security reasons. I also thought it would be easier to review/merge a patch if it is received as an attachment instead of inline. So what is the workflow after a patch is received via email? Is there some (automatic) tooling, or what is happening until a patch is merged? I'm accustomed to using the fork/commit/merge workflow that most projects with github/gitlab repositories have. I guess there is nothing like that (planned) in Yocto? Not that I want it currently, but who decides who will get commit access to the Yocto repos? > That being said, don't worry about re-submitting it, I can detach the > patch and apply it. Thanks for merging the patch into master! Will the patch also be merged into kirkstone? What is the workflow here?
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#7628): https://lists.yoctoproject.org/g/meta-virtualization/message/7628 Mute This Topic: https://lists.yoctoproject.org/mt/93801075/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
