From: Mark Hatle <mark.hatle@windriver.com>
To: akuster808 <akuster808@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
OpenEmbedded Devel List
<openembedded-devel@lists.openembedded.org>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [OE-core] patchwork
Date: Mon, 13 May 2019 10:32:48 +0300 [thread overview]
Message-ID: <bf12fd00-e786-25dc-4b10-056ce5adffb4@windriver.com> (raw)
In-Reply-To: <65432636-c595-ed39-28f3-efb7a0d565da@gmail.com>
On 5/12/19 9:04 PM, akuster808 wrote:
> ok, so no Admins. This is unexceptionable.
>
> OE TSC and Board, I believe its your time to get involved.
I've not used patchwork before, do you know who originally configured it? Was
it Paul Eggleton, or Richard, or? If I have an idea who was originally
responsible, I'm pretty sure we can figure out a handoff plan to someone else.
--Mark
> regards,
> Armin
>
> On 5/3/19 10:18 AM, akuster808 wrote:
>> Hello OE folk,
>>
>> My apologies for cross posting.
>>
>> Who is the Admin for Patchwork?
>>
>> I would like additional privileges to manage the "Yocto Project Layers"
>> queue.
>>
>> Also, I would like additional privileges to add new branches for any
>> oe, meta-oe queues & yp layers.
>>
>> kind regards,
>> Armin
>>
>
WARNING: multiple messages have this Message-ID (diff)
From: Mark Hatle <mark.hatle@windriver.com>
To: akuster808 <akuster808@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
OpenEmbedded Devel List
<openembedded-devel@lists.openembedded.org>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: patchwork
Date: Mon, 13 May 2019 10:32:48 +0300 [thread overview]
Message-ID: <bf12fd00-e786-25dc-4b10-056ce5adffb4@windriver.com> (raw)
In-Reply-To: <65432636-c595-ed39-28f3-efb7a0d565da@gmail.com>
On 5/12/19 9:04 PM, akuster808 wrote:
> ok, so no Admins. This is unexceptionable.
>
> OE TSC and Board, I believe its your time to get involved.
I've not used patchwork before, do you know who originally configured it? Was
it Paul Eggleton, or Richard, or? If I have an idea who was originally
responsible, I'm pretty sure we can figure out a handoff plan to someone else.
--Mark
> regards,
> Armin
>
> On 5/3/19 10:18 AM, akuster808 wrote:
>> Hello OE folk,
>>
>> My apologies for cross posting.
>>
>> Who is the Admin for Patchwork?
>>
>> I would like additional privileges to manage the "Yocto Project Layers"
>> queue.
>>
>> Also, I would like additional privileges to add new branches for any
>> oe, meta-oe queues & yp layers.
>>
>> kind regards,
>> Armin
>>
>
next prev parent reply other threads:[~2019-05-13 7:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 17:18 patchwork akuster808
2019-05-12 18:04 ` patchwork akuster808
2019-05-13 7:27 ` patchwork Zoran Stojsavljevic
2019-05-13 7:32 ` Mark Hatle [this message]
2019-05-13 7:32 ` patchwork Mark Hatle
2019-05-13 7:46 ` [yocto] [OE-core] patchwork Adrian Bunk
2019-05-13 7:46 ` Adrian Bunk
2019-05-13 7:46 ` [yocto] patchwork Adrian Bunk
2019-05-13 8:59 ` [yocto] [OE-core] patchwork Mark Hatle
2019-05-13 8:59 ` Mark Hatle
2019-05-13 8:59 ` [yocto] patchwork Mark Hatle
2019-05-13 16:56 ` Michael Halstead
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=bf12fd00-e786-25dc-4b10-056ce5adffb4@windriver.com \
--to=mark.hatle@windriver.com \
--cc=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=yocto@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.