[OE-core] oecommit ml

[Michael Halstead]

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 at lists.openembedded.org

We can mail openembedded-commits at lists.openembedded.org which would work
fine. Or I can create a bitbake-commits at lists.openembedded.org. Which is
better?

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 at yoctoproject.org> wrote:
>>
>> It seems git-notify was sending mail as "cia at 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 at 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 at gmail.com
>>>> --
>>>> _______________________________________________
>>>> Openembedded-core mailing list
>>>> Openembedded-core at lists.openembedded.org
>>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20151113/2865bdc0/attachment-0002.sig>