Re: [OE-core] [yocto] patchwork

[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 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.
>> http://git.yoctoproject.org/cgit/cgit.cgi/patchwork/
> No I mean who set it up for OE (or the YP) to use.  I don't even know at this
> point whose infrastructure the component runs on.  If I had that I'd know to
> start with either Tom or Michael.
>
> --Mark

I set the OE Patchwork up with Jose Lamego's help and maintain that
server now.


>>> --Mark
>> cu
>> Adrian
>>
-- 
Michael Halstead
Linux Foundation / SysAdmin

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [yocto] patchwork

[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 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.
> 
> http://git.yoctoproject.org/cgit/cgit.cgi/patchwork/

No I mean who set it up for OE (or the YP) to use.  I don't even know at this
point whose infrastructure the component runs on.  If I had that I'd know to
start with either Tom or Michael.

--Mark

>> --Mark
> 
> cu
> Adrian
> 

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [yocto] patchwork

[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
> 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.

http://git.yoctoproject.org/cgit/cgit.cgi/patchwork/

> --Mark

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

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

[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 a new thread instead.

This change adds the "[-t in_reply_to]" option, where "in_reply_to" is
the original cover letter's Message-Id, so this reference is added
to the new cover letter to ensure the thread continuity.

[YOCTO #11294]

Signed-off-by: Jose Lamego 
---
 scripts/create-pull-request | 17 +
 1 file changed, 13 insertions(+), 4 deletions(-)

diff --git a/scripts/create-pull-request b/scripts/create-pull-request
index e82858b..8f0be99 100755
--- a/scripts/create-pull-request
+++ b/scripts/create-pull-request
@@ -34,7 +34,7 @@ RFC=0
 usage() {
 CMD=$(basename $0)
 cat <"
 EOM
 }
 
 REMOTE="$CPR_CONTRIB_REMOTE"
 # Parse and validate arguments
-while getopts "b:acd:hi:m:o:p:r:s:u:l:" OPT; do
+while getopts "b:acd:hi:m:o:p:r:s:u:l:t:" OPT; do
case $OPT in
b)
BRANCH="$OPTARG"
@@ -108,7 +110,10 @@ while getopts "b:acd:hi:m:o:p:r:s:u:l:" OPT; do
a)
CPR_CONTRIB_AUTO_PUSH="1"
;;
-   esac
+t)
+IN_REPLY_TO="$OPTARG"
+;;
+esac
 done
 
 if [ -z "$REMOTE" ]; then
@@ -205,7 +210,11 @@ if [ -n "$RELDIR" ]; then
 fi
 
 # Generate the patches and cover letter
-git format-patch $extraopts -M40 --subject-prefix="$PREFIX" -n -o $ODIR 
--thread=shallow --cover-letter $RELATIVE_TO..$COMMIT_ID > /dev/null
+if [ -n "$IN_REPLY_TO" ]; then
+git format-patch $extraopts -M40 --subject-prefix="$PREFIX" -n -o $ODIR 
--thread=shallow --in-reply-to="$IN_REPLY_TO" --cover-letter 
$RELATIVE_TO..$COMMIT_ID > /dev/null
+else
+git format-patch $extraopts -M40 --subject-prefix="$PREFIX" -n -o $ODIR 
--thread=shallow --cover-letter $RELATIVE_TO..$COMMIT_ID > /dev/null
+fi
 
 if [ -z "$(ls -A $ODIR 2> /dev/null)" ]; then
 echo "ERROR: $ODIR is empty, no cover letter and patches was generated!"
-- 
2.7.4

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

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

[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.
> 
> If you are a Patchwork user please visit
> https://patchwork-next.openembedded.org/ and take a look. If you find
> anything amiss please e-mail me directly and include patchwork in the
> subject line.
> 
> Thank you for your help upgrading this important system!

I was using it to update meta-oe/master-next in last few days and it
seems to work the same as old patchwork for me.

But quite often I've noticed very slow response, is it running on
slower HW while testing or is the new version just a lot slower?

-- 
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com


signature.asc
Description: Digital signature
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core