public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ser, Simon" <simon.ser@intel.com>
To: "rhyskidd@gmail.com" <rhyskidd@gmail.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t] runner/executor: refactor error handling
Date: Thu, 21 Mar 2019 07:16:14 +0000	[thread overview]
Message-ID: <f4d633b44f305271f2d0bd26f15a1519f9ea2582.camel@intel.com> (raw)
In-Reply-To: <CA+iOQUHhEJuvZxcu1NXQ1bNqCrdsiPOaLz82LBDxUa0KESKNqw@mail.gmail.com>

On Thu, 2019-03-21 at 00:47 +1100, Rhys Kidd wrote:
> > Intel Finland Oy
> > Registered Address: PL 281, 00181 Helsinki 
> > Business Identity Code: 0357606 - 4 
> > Domiciled in Helsinki 
> > 
> > This e-mail and any attachments may contain confidential material
> > for
> > the sole use of the intended recipient(s). Any review or
> > distribution
> > by others is strictly prohibited. If you are not the intended
> > recipient, please contact the sender and delete all copies.
> 
> Hello Simon,
> 
> Welcome to igt.
>
> The above corporate boilerplate text should be removed from emails to
> public mailing lists, and definitely from emails with code that you
> are distributing under the MIT License.
> 
> I expect that you didn’t really intend for that paragraph to apply to
> your patch - but in particular the restrictions on distribution by
> others is problematic.
> 
> https://gitlab.freedesktop.org/drm/igt-gpu-tools/blob/master/CONTRIBUTING.md
> 
> You can read further there on the Developer’s Certificate of Origin
> that igt adopts and what it entails, which I understand is what you
> intended to use instead of this boilerplate.
> 
> Other Intel contributors might be able to assist you with whatever
> internal corporate proxy changes you need to make.

Hi,

Indeed, this disclaimer needs to go away. I've already taken action to
remove it, but it takes some time. Hopefully I'll soon be able to send
e-mails without it. In the meantime, we can hold off merging patches if
it causes legal issues (reviews still welcome!). I can re-send patches
without the disclaimer once it gets removed from my outgoing e-mails.

Thanks!
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki 
Business Identity Code: 0357606 - 4 
Domiciled in Helsinki 

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

      reply	other threads:[~2019-03-21  7:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-20  9:33 [igt-dev] [PATCH i-g-t] runner/executor: refactor error handling Ser, Simon
2019-03-20 10:19 ` Petri Latvala
2019-03-20 13:47 ` Rhys Kidd
2019-03-21  7:16   ` Ser, Simon [this message]

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=f4d633b44f305271f2d0bd26f15a1519f9ea2582.camel@intel.com \
    --to=simon.ser@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=rhyskidd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox