All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eddie Huang <eddie.huang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
To: Josh Triplett <josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org>
Cc: Chunfeng Yun
	<chunfeng.yun-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>,
	linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: Automated autobuilder emails.
Date: Fri, 29 Jul 2016 17:24:27 +0800	[thread overview]
Message-ID: <1469784267.12040.3.camel@mtksdaap41> (raw)
In-Reply-To: <20160729021658.GA15676@x>

Hi,

On Thu, 2016-07-28 at 19:16 -0700, Josh Triplett wrote:
> Hi,
> 
> I'm sending this to you because you're the two @mediatek.com folks
> listed in the kernel MAINTAINERS file, and other mediatek addresses I've
> tried have bounced.  I'm hoping you know the right people to contact and
> can forward this mail if needed.
> 
> It looks like mediatek has an internal autobuilder,
> adm_jenkins-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org , sending automated mails about kernel builds
> outside of Mediatek, to various people at Samsung, @google.com,
> @chromium.org, and myself.  Based on that selection of addresses, I'm
> guessing you're trying to run an autobuilder related to Chrome OS?
> 
> The autobuilder mails (sample below) include links to servers within
> mediatek, making them unhelpful for people outside of mediatek.  Could
> you please not send such mails to people outside your company?
> 
> If you're trying to run a build-checking service for people outside your
> company, you'd need to make the documentation and build logs accessible
> to people outside your company.  And if you're running an entirely
> internal autobuilder, it shouldn't be sending mails outside your
> company.
> 
> Thanks,
> Josh Triplett
> 

We already suspend our Jenkins auto build, and will modify mailing rule
to avoid sending mail outside Mediatek company.Sorry for your
inconvenience.

Eddie
Thanks

  reply	other threads:[~2016-07-29  9:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29  2:16 Automated autobuilder emails Josh Triplett
2016-07-29  9:24 ` Eddie Huang [this message]
2016-07-29  9:50   ` Josh Triplett

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=1469784267.12040.3.camel@mtksdaap41 \
    --to=eddie.huang-nus5lvnupcjwk0htik3j/w@public.gmane.org \
    --cc=chunfeng.yun-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
    --cc=josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org \
    --cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    /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.