From: Michael Halstead <mhalstead@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Yocto-mailing-list <yocto@lists.yoctoproject.org>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Denys Dmytriyenko <denis@denix.org>
Subject: Re: [yocto] [meta-lts-mixins][dunfell/go PATCH 1/4] Initial commit: add license, readme and layer config.
Date: Wed, 2 Feb 2022 15:50:06 -0800 [thread overview]
Message-ID: <CADfgfob5GLcopY=yCo5DuXTDR4ZUXTYPjErDmtnKt5jq6WJ6xQ@mail.gmail.com> (raw)
In-Reply-To: <CANNYZj_mmE-m0eW9SMjmQxr203B8THminnME_Os37dTET_rV-Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
Thank you for the ping. These branches are ready for you.
On Tue, Feb 1, 2022 at 6:23 AM Alexander Kanavin <alex.kanavin@gmail.com>
wrote:
> On Thu, 27 Jan 2022 at 21:06, Denys Dmytriyenko <denis@denix.org> wrote:
>
>> On Thu, Jan 27, 2022 at 06:07:06PM +0100, Alexander Kanavin wrote:
>> > A question specifically to Denys, how can I actually get this into the
>> > mixin repo, and have commit rights to the branch? We've tested this
>> quite
>> > well in private, and there are further enhancements coming up.
>>
>> Michael,
>>
>> Would it be possible to create 2 additional branches in the
>> meta-lts-mixins
>> repository at https://git.yoctoproject.org/meta-lts-mixins/ called
>> "dunfell/go" and also "dunfell/docker" and give Alex push rights to them?
>>
>> Please let us know, thanks a lot!
>>
>
> Ping, please :)
>
> Alex
>
--
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer
[-- Attachment #2: Type: text/html, Size: 1873 bytes --]
next prev parent reply other threads:[~2022-02-02 23:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16CE27BD1FB20052.24088@lists.yoctoproject.org>
2022-01-27 17:07 ` [yocto] [meta-lts-mixins][dunfell/go PATCH 1/4] Initial commit: add license, readme and layer config Alexander Kanavin
2022-01-27 18:02 ` Khem Raj
2022-01-27 20:06 ` Denys Dmytriyenko
2022-01-27 21:04 ` Khem Raj
2022-01-27 21:07 ` Alexander Kanavin
2022-02-01 14:23 ` Alexander Kanavin
2022-02-02 23:50 ` Michael Halstead [this message]
2022-02-03 10:16 ` Alexander Kanavin
2022-01-27 14:43 Alexander Kanavin
2022-01-27 14:48 ` [yocto] " Konrad Weihmann
2022-01-27 14:50 ` Alexander Kanavin
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='CADfgfob5GLcopY=yCo5DuXTDR4ZUXTYPjErDmtnKt5jq6WJ6xQ@mail.gmail.com' \
--to=mhalstead@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=denis@denix.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=yocto@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.