Before you ping some older patches

Before you ping some older patches

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 964 bytes --]

1) Make sure they aren't already in master (or master-next), currently
there is only one change in master-next:
eb7979113 netcat-openbsd: fix implicit dependency on pkg-config

2) Make sure there weren't some negative feedback comments on our change

3) Make sure the change made it to patchwork, currently there is only
one "open" change:
https://patchwork.openembedded.org/patch/137499/

Be aware that the changes are usually daily marked as archived, when
they are sorted to corresponding bundles and included in master-next
branch for testing, as described here:
http://www.openembedded.org/wiki/Patchwork#Multiple_layers_sharing_the_same_oe_project_on_patchwork

I'm writing this, because currently many changes are missing on patchwork,
because of some unknown issue with it, see:
http://lists.openembedded.org/pipermail/openembedded-devel/2017-February/111467.html
once this issue is resolved, please re-send missing changes.

Regards,

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

Re: Before you ping some older patches

[MacDonald, Joe]

It might just be me, but the list in general has seemed a bit off since at least Monday. I have good reason to believe it has eaten at least two of my posts.

-J.

On Feb 22, 2017 4:33 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
1) Make sure they aren't already in master (or master-next), currently
there is only one change in master-next:
eb7979113 netcat-openbsd: fix implicit dependency on pkg-config

2) Make sure there weren't some negative feedback comments on our change

3) Make sure the change made it to patchwork, currently there is only
one "open" change:
https://patchwork.openembedded.org/patch/137499/

Be aware that the changes are usually daily marked as archived, when
they are sorted to corresponding bundles and included in master-next
branch for testing, as described here:
http://www.openembedded.org/wiki/Patchwork#Multiple_layers_sharing_the_same_oe_project_on_patchwork

I'm writing this, because currently many changes are missing on patchwork,
because of some unknown issue with it, see:
http://lists.openembedded.org/pipermail/openembedded-devel/2017-February/111467.html
once this issue is resolved, please re-send missing changes.

Regards,

Re: Before you ping some older patches

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 1639 bytes --]

On Wed, Feb 22, 2017 at 10:26:54PM +0000, MacDonald, Joe wrote:
> It might just be me, but the list in general has seemed a bit off since at least Monday. I have good reason to believe it has eaten at least two of my posts.

During OEDAM discussion I also had a feeling that both my replies to
"Splitting meta-oe?" thread were eaten by the ML gremlins, but both
appear at:
http://lists.openembedded.org/pipermail/openembedded-devel/2017-February/thread.html
so that wasn't the case.

> On Feb 22, 2017 4:33 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> 1) Make sure they aren't already in master (or master-next), currently
> there is only one change in master-next:
> eb7979113 netcat-openbsd: fix implicit dependency on pkg-config
> 
> 2) Make sure there weren't some negative feedback comments on our change
> 
> 3) Make sure the change made it to patchwork, currently there is only
> one "open" change:
> https://patchwork.openembedded.org/patch/137499/
> 
> Be aware that the changes are usually daily marked as archived, when
> they are sorted to corresponding bundles and included in master-next
> branch for testing, as described here:
> http://www.openembedded.org/wiki/Patchwork#Multiple_layers_sharing_the_same_oe_project_on_patchwork
> 
> I'm writing this, because currently many changes are missing on patchwork,
> because of some unknown issue with it, see:
> http://lists.openembedded.org/pipermail/openembedded-devel/2017-February/111467.html
> once this issue is resolved, please re-send missing changes.
> 
> Regards,
> 

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

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

Re: Before you ping some older patches

[Michael Halstead]

The hooks are repaired and need testing. (Bad git/config settings.)
Please feel free to resubmit patches. Let me know if they do not appear
in patchwork.

I'm trying to see if I can automatically resend the missed patches and
mark them superseded if needed. I'll update post here if it works.


On 02/22/2017 01:32 PM, Martin Jansa wrote:
> 1) Make sure they aren't already in master (or master-next), currently
> there is only one change in master-next:
> eb7979113 netcat-openbsd: fix implicit dependency on pkg-config
>
> 2) Make sure there weren't some negative feedback comments on our change
>
> 3) Make sure the change made it to patchwork, currently there is only
> one "open" change:
> https://patchwork.openembedded.org/patch/137499/
>
> Be aware that the changes are usually daily marked as archived, when
> they are sorted to corresponding bundles and included in master-next
> branch for testing, as described here:
> http://www.openembedded.org/wiki/Patchwork#Multiple_layers_sharing_the_same_oe_project_on_patchwork
>
> I'm writing this, because currently many changes are missing on patchwork,
> because of some unknown issue with it, see:
> http://lists.openembedded.org/pipermail/openembedded-devel/2017-February/111467.html
> once this issue is resolved, please re-send missing changes.
>
> Regards,
>
>

-- 
Michael Halstead
Linux Foundation / SysAdmin

Re: Before you ping some older patches

[MacDonald, Joe]

I figured the same but there are at least two in my sent mail that are absent from the archives.  I'm inclined to blame a google apps hiccup since they're from my non-work address but I thought it worth mentioning anyway.

On Feb 22, 2017 5:51 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
On Wed, Feb 22, 2017 at 10:26:54PM +0000, MacDonald, Joe wrote:
> It might just be me, but the list in general has seemed a bit off since at least Monday. I have good reason to believe it has eaten at least two of my posts.

During OEDAM discussion I also had a feeling that both my replies to
"Splitting meta-oe?" thread were eaten by the ML gremlins, but both
appear at:
http://lists.openembedded.org/pipermail/openembedded-devel/2017-February/thread.html
so that wasn't the case.

> On Feb 22, 2017 4:33 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> 1) Make sure they aren't already in master (or master-next), currently
> there is only one change in master-next:
> eb7979113 netcat-openbsd: fix implicit dependency on pkg-config
>
> 2) Make sure there weren't some negative feedback comments on our change
>
> 3) Make sure the change made it to patchwork, currently there is only
> one "open" change:
> https://patchwork.openembedded.org/patch/137499/
>
> Be aware that the changes are usually daily marked as archived, when
> they are sorted to corresponding bundles and included in master-next
> branch for testing, as described here:
> http://www.openembedded.org/wiki/Patchwork#Multiple_layers_sharing_the_same_oe_project_on_patchwork
>
> I'm writing this, because currently many changes are missing on patchwork,
> because of some unknown issue with it, see:
> http://lists.openembedded.org/pipermail/openembedded-devel/2017-February/111467.html
> once this issue is resolved, please re-send missing changes.
>
> Regards,
>

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

Re: Before you ping some older patches

[Martin Jansa]

Hi Michael,

thanks for quick fix.

The hook now shows error about sendmail I wasn't seeing before:

OE @ ~/meta-openembedded $ git push origin master-next
Counting objects: 78, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (25/25), done.
Writing objects: 100% (78/78), 7.35 KiB | 0 bytes/s, done.
Total 78 (delta 56), reused 66 (delta 49)
remote: No sendmail executable found.  Try setting
multimailhook.sendmailCommand.
To git.openembedded.org:meta-openembedded
   eb7979113..0d27137f0  master-next -> master-next


On Thu, Feb 23, 2017 at 12:06 AM, Michael Halstead <
mhalstead@linuxfoundation.org> wrote:

> The hooks are repaired and need testing. (Bad git/config settings.) Please
> feel free to resubmit patches. Let me know if they do not appear in
> patchwork.
> I'm trying to see if I can automatically resend the missed patches and
> mark them superseded if needed. I'll update post here if it works.
>
>
>
> On 02/22/2017 01:32 PM, Martin Jansa wrote:
>
> 1) Make sure they aren't already in master (or master-next), currently
> there is only one change in master-next:
> eb7979113 netcat-openbsd: fix implicit dependency on pkg-config
>
> 2) Make sure there weren't some negative feedback comments on our change
>
> 3) Make sure the change made it to patchwork, currently there is only
> one "open" change:https://patchwork.openembedded.org/patch/137499/
>
> Be aware that the changes are usually daily marked as archived, when
> they are sorted to corresponding bundles and included in master-next
> branch for testing, as described here:http://www.openembedded.org/wiki/Patchwork#Multiple_layers_sharing_the_same_oe_project_on_patchwork
>
> I'm writing this, because currently many changes are missing on patchwork,
> because of some unknown issue with it, see:http://lists.openembedded.org/pipermail/openembedded-devel/2017-February/111467.html
> once this issue is resolved, please re-send missing changes.
>
> Regards,
>
>
>
>
> --
> Michael Halstead
> Linux Foundation / SysAdmin
>
>

Re: Before you ping some older patches

[Michael Halstead]

[-- Attachment #1.1.1: Type: text/plain, Size: 2747 bytes --]


On 02/22/2017 03:48 PM, Martin Jansa wrote:
> Hi Michael,
>
> thanks for quick fix.
>
> The hook now shows error about sendmail I wasn't seeing before:

I've reinstalled mailutils and the mail daemon, Can you please try
pushing again.

>
> OE @ ~/meta-openembedded $ git push origin master-next 
> Counting objects: 78, done.
> Delta compression using up to 8 threads.
> Compressing objects: 100% (25/25), done.
> Writing objects: 100% (78/78), 7.35 KiB | 0 bytes/s, done.
> Total 78 (delta 56), reused 66 (delta 49)
> remote: No sendmail executable found.  Try setting
> multimailhook.sendmailCommand.
> To git.openembedded.org:meta-openembedded
>    eb7979113..0d27137f0  master-next -> master-next
>
>
> On Thu, Feb 23, 2017 at 12:06 AM, Michael Halstead
> <mhalstead@linuxfoundation.org <mailto:mhalstead@linuxfoundation.org>>
> wrote:
>
>     The hooks are repaired and need testing. (Bad git/config
>     settings.) Please feel free to resubmit patches. Let me know if
>     they do not appear in patchwork.
>
>     I'm trying to see if I can automatically resend the missed patches
>     and mark them superseded if needed. I'll update post here if it
>     works.
>
>
>
>     On 02/22/2017 01:32 PM, Martin Jansa wrote:
>>     1) Make sure they aren't already in master (or master-next), currently
>>     there is only one change in master-next:
>>     eb7979113 netcat-openbsd: fix implicit dependency on pkg-config
>>
>>     2) Make sure there weren't some negative feedback comments on our change
>>
>>     3) Make sure the change made it to patchwork, currently there is only
>>     one "open" change:
>>     https://patchwork.openembedded.org/patch/137499/
>>     <https://patchwork.openembedded.org/patch/137499/>
>>
>>     Be aware that the changes are usually daily marked as archived, when
>>     they are sorted to corresponding bundles and included in master-next
>>     branch for testing, as described here:
>>     http://www.openembedded.org/wiki/Patchwork#Multiple_layers_sharing_the_same_oe_project_on_patchwork
>>     <http://www.openembedded.org/wiki/Patchwork#Multiple_layers_sharing_the_same_oe_project_on_patchwork>
>>
>>     I'm writing this, because currently many changes are missing on patchwork,
>>     because of some unknown issue with it, see:
>>     http://lists.openembedded.org/pipermail/openembedded-devel/2017-February/111467.html
>>     <http://lists.openembedded.org/pipermail/openembedded-devel/2017-February/111467.html>
>>     once this issue is resolved, please re-send missing changes.
>>
>>     Regards,
>>
>     -- 
>     Michael Halstead
>     Linux Foundation / SysAdmin
>
-- 
Michael Halstead
Linux Foundation / SysAdmin

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: Before you ping some older patches

[Derek Straka]

I resubmitted each of the patches (as V2s) that didn't make it into
master-next.  If we miss any patches in meta-python, I will catch it with
my nightly CI run, so there isn't a need to write a script to search for
missing patches there.  Thanks.

-Derek

On Wed, Feb 22, 2017 at 6:48 PM, Martin Jansa <martin.jansa@gmail.com>
wrote:

> Hi Michael,
>
> thanks for quick fix.
>
> The hook now shows error about sendmail I wasn't seeing before:
>
> OE @ ~/meta-openembedded $ git push origin master-next
> Counting objects: 78, done.
> Delta compression using up to 8 threads.
> Compressing objects: 100% (25/25), done.
> Writing objects: 100% (78/78), 7.35 KiB | 0 bytes/s, done.
> Total 78 (delta 56), reused 66 (delta 49)
> remote: No sendmail executable found.  Try setting
> multimailhook.sendmailCommand.
> To git.openembedded.org:meta-openembedded
>    eb7979113..0d27137f0  master-next -> master-next
>
>
> On Thu, Feb 23, 2017 at 12:06 AM, Michael Halstead <
> mhalstead@linuxfoundation.org> wrote:
>
> > The hooks are repaired and need testing. (Bad git/config settings.)
> Please
> > feel free to resubmit patches. Let me know if they do not appear in
> > patchwork.
> > I'm trying to see if I can automatically resend the missed patches and
> > mark them superseded if needed. I'll update post here if it works.
> >
> >
> >
> > On 02/22/2017 01:32 PM, Martin Jansa wrote:
> >
> > 1) Make sure they aren't already in master (or master-next), currently
> > there is only one change in master-next:
> > eb7979113 netcat-openbsd: fix implicit dependency on pkg-config
> >
> > 2) Make sure there weren't some negative feedback comments on our change
> >
> > 3) Make sure the change made it to patchwork, currently there is only
> > one "open" change:https://patchwork.openembedded.org/patch/137499/
> >
> > Be aware that the changes are usually daily marked as archived, when
> > they are sorted to corresponding bundles and included in master-next
> > branch for testing, as described here:http://www.openembedded.
> org/wiki/Patchwork#Multiple_layers_sharing_the_same_oe_
> project_on_patchwork
> >
> > I'm writing this, because currently many changes are missing on
> patchwork,
> > because of some unknown issue with it, see:http://lists.openembedded.
> org/pipermail/openembedded-devel/2017-February/111467.html
> > once this issue is resolved, please re-send missing changes.
> >
> > Regards,
> >
> >
> >
> >
> > --
> > Michael Halstead
> > Linux Foundation / SysAdmin
> >
> >
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>

Re: Before you ping some older patches

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 3790 bytes --]

On Thu, Feb 23, 2017 at 12:48:22AM +0100, Martin Jansa wrote:
> Hi Michael,
> 
> thanks for quick fix.
> 
> The hook now shows error about sendmail I wasn't seeing before:
> 
> OE @ ~/meta-openembedded $ git push origin master-next
> Counting objects: 78, done.
> Delta compression using up to 8 threads.
> Compressing objects: 100% (25/25), done.
> Writing objects: 100% (78/78), 7.35 KiB | 0 bytes/s, done.
> Total 78 (delta 56), reused 66 (delta 49)
> remote: No sendmail executable found.  Try setting
> multimailhook.sendmailCommand.
> To git.openembedded.org:meta-openembedded
>    eb7979113..0d27137f0  master-next -> master-next

Now it found some sendmail... 

OE @ ~/meta-openembedded $ git push origin master-next 
Counting objects: 85, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (71/71), done.
Writing objects: 100% (85/85), 18.90 KiB | 0 bytes/s, done.
Total 85 (delta 47), reused 0 (delta 0)
remote: Sending notification emails to: openembedded-commits@lists.openembedded.org.
remote: 
remote: Exception 'CommandError' raised. Please report this as a bug to
remote: https://github.com/git-multimail/git-multimail/issues
remote: with the information below:
remote: 
remote: git-multimail version 1.2.0
remote: Python version 2.7.12 (default, Nov 19 2016, 06:48:10) 
remote: [GCC 5.4.0 20160609]
remote: Traceback (most recent call last):
remote:   File "/home/git/bin/git_multimail.py", line 3729, in main
remote:     run_as_post_receive_hook(environment, mailer)
remote:   File "/home/git/bin/git_multimail.py", line 3386, in run_as_post_receive_hook
remote:     push.send_emails(mailer, body_filter=environment.filter_body)
remote:   File "/home/git/bin/git_multimail.py", line 3332, in send_emails
remote:     change.recipients,
remote:   File "/home/git/bin/git_multimail.py", line 1883, in send
remote:     raise CommandError(self.command, retcode)
remote: CommandError: Command "/usr/sbin/sendmail -oi -t" failed with retcode 1
To git.openembedded.org:meta-openembedded
   0d27137f0..57115ebc1  master-next -> master-next


> On Thu, Feb 23, 2017 at 12:06 AM, Michael Halstead <
> mhalstead@linuxfoundation.org> wrote:
> 
> > The hooks are repaired and need testing. (Bad git/config settings.) Please
> > feel free to resubmit patches. Let me know if they do not appear in
> > patchwork.
> > I'm trying to see if I can automatically resend the missed patches and
> > mark them superseded if needed. I'll update post here if it works.
> >
> >
> >
> > On 02/22/2017 01:32 PM, Martin Jansa wrote:
> >
> > 1) Make sure they aren't already in master (or master-next), currently
> > there is only one change in master-next:
> > eb7979113 netcat-openbsd: fix implicit dependency on pkg-config
> >
> > 2) Make sure there weren't some negative feedback comments on our change
> >
> > 3) Make sure the change made it to patchwork, currently there is only
> > one "open" change:https://patchwork.openembedded.org/patch/137499/
> >
> > Be aware that the changes are usually daily marked as archived, when
> > they are sorted to corresponding bundles and included in master-next
> > branch for testing, as described here:http://www.openembedded.org/wiki/Patchwork#Multiple_layers_sharing_the_same_oe_project_on_patchwork
> >
> > I'm writing this, because currently many changes are missing on patchwork,
> > because of some unknown issue with it, see:http://lists.openembedded.org/pipermail/openembedded-devel/2017-February/111467.html
> > once this issue is resolved, please re-send missing changes.
> >
> > Regards,
> >
> >
> >
> >
> > --
> > Michael Halstead
> > Linux Foundation / SysAdmin
> >
> >

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

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

Re: Before you ping some older patches

[Michael Halstead]

On 02/22/2017 05:53 PM, Martin Jansa wrote:
> On Thu, Feb 23, 2017 at 12:48:22AM +0100, Martin Jansa wrote:
>> Hi Michael,
>>
>> thanks for quick fix.
>>
>> The hook now shows error about sendmail I wasn't seeing before:
>>
>> OE @ ~/meta-openembedded $ git push origin master-next
>> Counting objects: 78, done.
>> Delta compression using up to 8 threads.
>> Compressing objects: 100% (25/25), done.
>> Writing objects: 100% (78/78), 7.35 KiB | 0 bytes/s, done.
>> Total 78 (delta 56), reused 66 (delta 49)
>> remote: No sendmail executable found.  Try setting
>> multimailhook.sendmailCommand.
>> To git.openembedded.org:meta-openembedded
>>    eb7979113..0d27137f0  master-next -> master-next
> Now it found some sendmail... 
>
> OE @ ~/meta-openembedded $ git push origin master-next 
> Counting objects: 85, done.
> Delta compression using up to 8 threads.
> Compressing objects: 100% (71/71), done.
> Writing objects: 100% (85/85), 18.90 KiB | 0 bytes/s, done.
> Total 85 (delta 47), reused 0 (delta 0)
> remote: Sending notification emails to: openembedded-commits@lists.openembedded.org.
> remote: 
> remote: Exception 'CommandError' raised. Please report this as a bug to
> remote: https://github.com/git-multimail/git-multimail/issues
> remote: with the information below:
> remote: 
> remote: git-multimail version 1.2.0
> remote: Python version 2.7.12 (default, Nov 19 2016, 06:48:10) 
> remote: [GCC 5.4.0 20160609]
> remote: Traceback (most recent call last):
> remote:   File "/home/git/bin/git_multimail.py", line 3729, in main
> remote:     run_as_post_receive_hook(environment, mailer)
> remote:   File "/home/git/bin/git_multimail.py", line 3386, in run_as_post_receive_hook
> remote:     push.send_emails(mailer, body_filter=environment.filter_body)
> remote:   File "/home/git/bin/git_multimail.py", line 3332, in send_emails
> remote:     change.recipients,
> remote:   File "/home/git/bin/git_multimail.py", line 1883, in send
> remote:     raise CommandError(self.command, retcode)
> remote: CommandError: Command "/usr/sbin/sendmail -oi -t" failed with retcode 1
> To git.openembedded.org:meta-openembedded
>    0d27137f0..57115ebc1  master-next -> master-next
I'm adding a temporary repo to test this before having you test again
since the issues are extensive. I'll follow up shortly.
>
>> On Thu, Feb 23, 2017 at 12:06 AM, Michael Halstead <
>> mhalstead@linuxfoundation.org> wrote:
>>
>>> The hooks are repaired and need testing. (Bad git/config settings.) Please
>>> feel free to resubmit patches. Let me know if they do not appear in
>>> patchwork.
>>> I'm trying to see if I can automatically resend the missed patches and
>>> mark them superseded if needed. I'll update post here if it works.
>>>
>>>
>>>
>>> On 02/22/2017 01:32 PM, Martin Jansa wrote:
>>>
>>> 1) Make sure they aren't already in master (or master-next), currently
>>> there is only one change in master-next:
>>> eb7979113 netcat-openbsd: fix implicit dependency on pkg-config
>>>
>>> 2) Make sure there weren't some negative feedback comments on our change
>>>
>>> 3) Make sure the change made it to patchwork, currently there is only
>>> one "open" change:https://patchwork.openembedded.org/patch/137499/
>>>
>>> Be aware that the changes are usually daily marked as archived, when
>>> they are sorted to corresponding bundles and included in master-next
>>> branch for testing, as described here:http://www.openembedded.org/wiki/Patchwork#Multiple_layers_sharing_the_same_oe_project_on_patchwork
>>>
>>> I'm writing this, because currently many changes are missing on patchwork,
>>> because of some unknown issue with it, see:http://lists.openembedded.org/pipermail/openembedded-devel/2017-February/111467.html
>>> once this issue is resolved, please re-send missing changes.
>>>
>>> Regards,
>>>
>>>
>>>
>>>
>>> --
>>> Michael Halstead
>>> Linux Foundation / SysAdmin
>>>
>>>

-- 
Michael Halstead
Linux Foundation / SysAdmin

Re: Before you ping some older patches

[Michael Halstead]

On 02/22/2017 05:58 PM, Michael Halstead wrote:
>
> On 02/22/2017 05:53 PM, Martin Jansa wrote:
>> On Thu, Feb 23, 2017 at 12:48:22AM +0100, Martin Jansa wrote:
>>> Hi Michael,
>>>
>>> thanks for quick fix.
>>>
>>> The hook now shows error about sendmail I wasn't seeing before:
>>>
>>> OE @ ~/meta-openembedded $ git push origin master-next
>>> Counting objects: 78, done.
>>> Delta compression using up to 8 threads.
>>> Compressing objects: 100% (25/25), done.
>>> Writing objects: 100% (78/78), 7.35 KiB | 0 bytes/s, done.
>>> Total 78 (delta 56), reused 66 (delta 49)
>>> remote: No sendmail executable found.  Try setting
>>> multimailhook.sendmailCommand.
>>> To git.openembedded.org:meta-openembedded
>>>    eb7979113..0d27137f0  master-next -> master-next
>> Now it found some sendmail... 
>>
>> OE @ ~/meta-openembedded $ git push origin master-next 
>> Counting objects: 85, done.
>> Delta compression using up to 8 threads.
>> Compressing objects: 100% (71/71), done.
>> Writing objects: 100% (85/85), 18.90 KiB | 0 bytes/s, done.
>> Total 85 (delta 47), reused 0 (delta 0)
>> remote: Sending notification emails to: openembedded-commits@lists.openembedded.org.
>> remote: 
>> remote: Exception 'CommandError' raised. Please report this as a bug to
>> remote: https://github.com/git-multimail/git-multimail/issues
>> remote: with the information below:
>> remote: 
>> remote: git-multimail version 1.2.0
>> remote: Python version 2.7.12 (default, Nov 19 2016, 06:48:10) 
>> remote: [GCC 5.4.0 20160609]
>> remote: Traceback (most recent call last):
>> remote:   File "/home/git/bin/git_multimail.py", line 3729, in main
>> remote:     run_as_post_receive_hook(environment, mailer)
>> remote:   File "/home/git/bin/git_multimail.py", line 3386, in run_as_post_receive_hook
>> remote:     push.send_emails(mailer, body_filter=environment.filter_body)
>> remote:   File "/home/git/bin/git_multimail.py", line 3332, in send_emails
>> remote:     change.recipients,
>> remote:   File "/home/git/bin/git_multimail.py", line 1883, in send
>> remote:     raise CommandError(self.command, retcode)
>> remote: CommandError: Command "/usr/sbin/sendmail -oi -t" failed with retcode 1
>> To git.openembedded.org:meta-openembedded
>>    0d27137f0..57115ebc1  master-next -> master-next
> I'm adding a temporary repo to test this before having you test again
> since the issues are extensive. I'll follow up shortly.
I had configured the following and the trailing . was causing sendmail
to fail.

    mailingList = openembedded-commits@lists.openembedded.org.

I've removed the . and now my tests are succeeding.

Thank you for helping me troubleshoot this.

>>> On Thu, Feb 23, 2017 at 12:06 AM, Michael Halstead <
>>> mhalstead@linuxfoundation.org> wrote:
>>>
>>>> The hooks are repaired and need testing. (Bad git/config settings.) Please
>>>> feel free to resubmit patches. Let me know if they do not appear in
>>>> patchwork.
>>>> I'm trying to see if I can automatically resend the missed patches and
>>>> mark them superseded if needed. I'll update post here if it works.
>>>>
>>>>
>>>>
>>>> On 02/22/2017 01:32 PM, Martin Jansa wrote:
>>>>
>>>> 1) Make sure they aren't already in master (or master-next), currently
>>>> there is only one change in master-next:
>>>> eb7979113 netcat-openbsd: fix implicit dependency on pkg-config
>>>>
>>>> 2) Make sure there weren't some negative feedback comments on our change
>>>>
>>>> 3) Make sure the change made it to patchwork, currently there is only
>>>> one "open" change:https://patchwork.openembedded.org/patch/137499/
>>>>
>>>> Be aware that the changes are usually daily marked as archived, when
>>>> they are sorted to corresponding bundles and included in master-next
>>>> branch for testing, as described here:http://www.openembedded.org/wiki/Patchwork#Multiple_layers_sharing_the_same_oe_project_on_patchwork
>>>>
>>>> I'm writing this, because currently many changes are missing on patchwork,
>>>> because of some unknown issue with it, see:http://lists.openembedded.org/pipermail/openembedded-devel/2017-February/111467.html
>>>> once this issue is resolved, please re-send missing changes.
>>>>
>>>> Regards,
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Michael Halstead
>>>> Linux Foundation / SysAdmin
>>>>
>>>>

-- 
Michael Halstead
Linux Foundation / SysAdmin