Re: oecommit ml

[Michael Halstead <michael@yoctoproject.org>]

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


On 11/13/2015 01:50 PM, Khem Raj wrote:
>> On Nov 13, 2015, at 1:45 PM, Michael Halstead <michael@yoctoproject.org> wrote:
>>
>> Bitbake is disabled with the note:
>>
>> # interferes with patchwork sice it sends emails after the patches are
>> closed
>> # we could re-enable it if the mails went to someother ml may be
>> bitbake-commits
>>
>> This happens because it was mailing bitbake-devel@lists.openembedded.org
>>
>> We can mail openembedded-commits@lists.openembedded.org which would work
>> fine. Or I can create a bitbake-commits@lists.openembedded.org. Which is
>> better?
> I think mailing to openembedded-commits@lists.openembedded.org might be ok. with [bitbake] in message subject for filtering help.

I've altered the script to include [reponame] in the subject of all
e-mails and enabled for bitbake.


Michael Halstead
Yocto Project / SysAdmin


>
>> Michael Halstead
>> Yocto Project / SysAdmin
>>
>> On 11/13/2015 01:41 PM, Khem Raj wrote:
>>>> On Nov 13, 2015, at 1:39 PM, Michael Halstead <michael@yoctoproject.org> wrote:
>>>>
>>>> It seems git-notify was sending mail as "cia@cia.navi.cx" and that was
>>>> causing the mail server to get added to blacklists so it was disabled.
>>>> I've changed the script and re-enabled it for:
>>>>
>>>> openembedded-core
>>>> meta-openembedded
>>>> OpenEmbedded (but I don't know if we need it)
>>> bitbake too plz.
>>>
>>>> Michael Halstead
>>>> Yocto Project / SysAdmin
>>>>
>>>> On 11/13/2015 12:47 PM, Khem Raj wrote:
>>>>>> On Nov 13, 2015, at 3:59 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
>>>>>>
>>>>>> On Thu, Nov 12, 2015 at 06:14:14PM -0500, Trevor Woerner wrote:
>>>>>>> It seems I missed some announcement. At first I thought I had been
>>>>>>> unsubscribed from the openembedded-commits mailing list (since I haven't
>>>>>>> received any emails on that list since about the end of September). So I
>>>>>>> looked up http://lists.openembedded.org/pipermail/openembedded-commits/
>>>>>>> and it seems to have gone quiet about that time too.
>>>>>> I've already asked Paul and Michael few times on IRC in last few weeks.
>>>>>>
>>>>>> I haven't received any reply from Michael, adding him to To, now.
>>>>> I see that git-notify hooks have been disabled explicitly for all repos in update.secondary file. thats why the messages are not being
>>>>> sent. We can enable them but I would like to know the reason they were disabled in first place. Since we do not have this under some
>>>>> sort of revision history, I can not find information for them as well. So we need this info before we enable them back.
>>>>>
>>>>>>> I liked being able to watch the commits to see what was going in, and to
>>>>>>> check if my patches were added (before sending "ping"s, without having
>>>>>>> to "git pull" and search). Is there a new workflow for seeing what's
>>>>>>> going in?
>>>>>> Yes, I find them useful too (e.g. to report issue with commit which was
>>>>>> recently merged) or in general to know that it's worth doing "git pull".
>>>>>>
>>>>>> --
>>>>>> Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com
>>>>>> --
>>>>>> _______________________________________________
>>>>>> Openembedded-core mailing list
>>>>>> Openembedded-core@lists.openembedded.org
>>>>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>



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