From: Gary Oblock <gary@amperecomputing.com>
To: "Gabriel Ravier" <gabravier@gmail.com>,
"Martin Liška" <mliska@suse.cz>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Issue with a flag that I defined getting set to zero
Date: Fri, 7 Jan 2022 09:18:37 +0000 [thread overview]
Message-ID: <BYAPR01MB5464580C6EF2ACD0EA44109BC64D9@BYAPR01MB5464.prod.exchangelabs.com> (raw)
In-Reply-To: <27083d15-b33a-e4c0-a48f-9f187b5f5a25@gmail.com>
Gabriel,
Yes, indeed, thank you.
Note, it is a reminder to those that are receiving proprietary
and that is considered as a legal obligation on the part of the
company transmitting it because they must make an effort to
protect their proprietary information.
I'm not a lawyer either but I feel like I'm being forced to
act like one. 😉
Now, can anybody answer my question?
Sincerely
Gary
________________________________
From: Gabriel Ravier <gabravier@gmail.com>
Sent: Friday, January 7, 2022 12:56 AM
To: Martin Liška <mliska@suse.cz>; Gary Oblock <gary@amperecomputing.com>; gcc@gcc.gnu.org <gcc@gcc.gnu.org>
Subject: Re: Issue with a flag that I defined getting set to zero
[EXTERNAL EMAIL NOTICE: This email originated from an external sender. Please be mindful of safe email handling and proprietary information protection practices.]
On 1/7/22 09:38, Martin Liška wrote:
> On 1/7/22 09:30, Gary Oblock wrote:
>> Regarding the corporate legal gibberish. It's automatic
>> and not under my control also we're not supposed to
>> use private emails for work...
>
> I respect that. But please respect me that I won't reply to your
> emails any longer. I don't want to follow the conditions in the NOTICE!
>
> Cheers,
> Martin
>
As far as I know the notice has no legal significance at all (which Gary
should probably point out to his management. Really, pretty much the
only thing the disclaimer will do is that _some_ people _might_ read it
and _some_ of those people _might_ adhere to the terms given there,
which is basically meaningless compared to the general annoyance
resulting from disclaimers being at the end of e-mails everywhere). You
can't just magically establish an agreement that results in a duty of
nondisclosure like this without agreement, and just receiving an email
obviously isn't that.
(although ironically, I guess I should add a disclaimer of my own: I
ain't a lawyer and this isn't legal advice)
next prev parent reply other threads:[~2022-01-07 9:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 8:10 Gary Oblock
2022-01-07 8:20 ` Martin Liška
2022-01-07 8:30 ` Gary Oblock
2022-01-07 8:38 ` Martin Liška
2022-01-07 8:56 ` Gabriel Ravier
2022-01-07 9:18 ` Gary Oblock [this message]
2022-01-10 8:36 ` Richard Biener
2022-01-10 19:53 ` Gary Oblock
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=BYAPR01MB5464580C6EF2ACD0EA44109BC64D9@BYAPR01MB5464.prod.exchangelabs.com \
--to=gary@amperecomputing.com \
--cc=gabravier@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=mliska@suse.cz \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).