From: Guenther Meyer <g.meyer@signum-media.de>
To: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization] [PATCH] fixed typos in kubernetes recipe
Date: Mon, 26 Sep 2022 10:24:07 +0200 [thread overview]
Message-ID: <20220926102346.7a0d6fbb@serenity> (raw)
In-Reply-To: <CADkTA4PZY7rBbQwN1AH2D+AWxAqYi5ndmvGwvxmL-xMdPtuFdg@mail.gmail.com>
On Tue, 20 Sep 2022 08:03:21 -0400
"Bruce Ashfield" <bruce.ashfield@gmail.com> 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?
next prev parent reply other threads:[~2022-09-26 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 11:34 [PATCH] fixed typos in kubernetes recipe Guenther Meyer
2022-09-20 12:03 ` [meta-virtualization] " Bruce Ashfield
2022-09-26 8:24 ` Guenther Meyer [this message]
2022-09-26 12:48 ` Bruce Ashfield
2022-09-30 9:31 ` Guenther Meyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220926102346.7a0d6fbb@serenity \
--to=g.meyer@signum-media.de \
--cc=meta-virtualization@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.