Re: [OE-core] [yocto] patchwork

2019-05-13 Thread Michael Halstead
On 5/13/19 1:59 AM, Mark Hatle wrote: > On 5/13/19 10:46 AM, Adrian Bunk wrote: >> On Mon, May 13, 2019 at 10:32:48AM +0300, Mark Hatle wrote: >>> 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 invol

Re: [OE-core] [yocto] patchwork

2019-05-13 Thread Mark Hatle
On 5/13/19 10:46 AM, Adrian Bunk wrote: > On Mon, May 13, 2019 at 10:32:48AM +0300, Mark Hatle wrote: >> 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 y

Re: [OE-core] [yocto] patchwork

2019-05-13 Thread Adrian Bunk
On Mon, May 13, 2019 at 10:32:48AM +0300, Mark Hatle wrote: > 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

[OE-core] [yocto][patchwork][PATCH v2] create-pull-request: add "-t in-reply-to" option

2017-04-05 Thread Jose Lamego
The create-pull-request script creates patches as replies to a cover letter, in the form of an email thread. If further revisions are sent to the mailing list without referencing to the first revision, these new revisions are not identified at the mailing list as part of the original thread, but as

Re: [OE-core] [yocto] Patchwork users: Help test new version

2016-06-23 Thread Martin Jansa
On Mon, Jun 20, 2016 at 10:47:16AM -0700, Michael Halstead wrote: > Hello, > > OpenEmbedded is nearly ready to upgrade to a new version of Patchwork. > The new version offers several new features that will allow OpenEmbedded > to improve developer workflow and automated checks on incoming patches.