From: Michael Halstead <michael@yoctoproject.org>
To: Khem Raj <raj.khem@gmail.com>, Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: oecommit ml
Date: Fri, 13 Nov 2015 13:39:44 -0800 [thread overview]
Message-ID: <564658A0.60609@yoctoproject.org> (raw)
In-Reply-To: <056F5AC5-DD52-4BF7-B88D-4312C40DFA2A@gmail.com>
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)
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
next prev parent reply other threads:[~2015-11-13 21:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 23:14 oecommit ml Trevor Woerner
2015-11-13 11:59 ` Martin Jansa
2015-11-13 20:47 ` Khem Raj
2015-11-13 21:39 ` Michael Halstead [this message]
2015-11-13 21:41 ` Khem Raj
2015-11-13 21:45 ` Michael Halstead
2015-11-13 21:50 ` Khem Raj
2015-11-13 22:03 ` Michael Halstead
2015-11-16 20:52 ` Martin Jansa
2015-11-16 20:56 ` Martin Jansa
2015-11-16 21:56 ` Michael Halstead
[not found] ` <5659F2A0.7070003@gmail.com>
2016-02-16 16:40 ` Trevor Woerner
2016-02-16 16:53 ` Martin Jansa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=564658A0.60609@yoctoproject.org \
--to=michael@yoctoproject.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.