From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: Julien Desfossez <ju@klipix.org>
Cc: Jeremie Galarneau <jgalar@efficios.com>,
lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] Transfer of LTTng copyright ownership: Julien Desfossez
Date: Fri, 14 Jan 2022 15:12:15 -0500 (EST) [thread overview]
Message-ID: <25936100.34106.1642191135598.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <f43c86fa-3f65-c97a-e411-44bb886845e4@klipix.org>
----- On Jan 14, 2022, at 2:51 PM, Julien Desfossez ju@klipix.org wrote:
> On 2022-01-14 2:49 p.m., Mathieu Desnoyers wrote:
>> Hi Julien,
>>
>> In order to facilitate maintenance of the LTTng project, would you agree to
>> transfer your copyright ownership for code authored outside of your employment
>> at EfficiOS to EfficiOS Inc. ?
>>
>> This particularly affects the lttng-tools, lttng-ust and lttng-modules files
>> with copyright:
>>
>> Copyright (C) 201N Julien Desfossez <julien.desfossez@polymtl.ca>
> Yes, no problem !
Great, I will CC you on the patches applying the copyright ownership transfer.
Please reply to them publicly with your Signed-off-by tag so I can add it
before merging them.
Thanks,
Mathieu
>
>> Thanks for all your contributions to LTTng !
>>
>> Mathieu
>
> Thanks !
>
> Julien
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
prev parent reply other threads:[~2022-01-14 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 19:49 [lttng-dev] Transfer of LTTng copyright ownership: Julien Desfossez Mathieu Desnoyers via lttng-dev
2022-01-14 19:51 ` Julien Desfossez via lttng-dev
2022-01-14 20:12 ` Mathieu Desnoyers via lttng-dev [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=25936100.34106.1642191135598.JavaMail.zimbra@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=jgalar@efficios.com \
--cc=ju@klipix.org \
--cc=mathieu.desnoyers@efficios.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;
as well as URLs for NNTP newsgroup(s).