mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: David Wang <00107082@163.com>
Cc: musl@lists.openwall.com
Subject: Re: [musl] Compile gcc-12 with musl and report errors
Date: Mon, 13 Feb 2023 09:26:32 -0500	[thread overview]
Message-ID: <20230213142632.GS4163@brightrain.aerifal.cx> (raw)
In-Reply-To: <1173336c.4e76.1864b2350d2.Coremail.00107082@163.com>

On Mon, Feb 13, 2023 at 10:17:31PM +0800, David Wang wrote:
> 
> 在 2023-02-13 22:12:38,"alice" <alice@ayaya.dev> 写道:
> 
> >> 本邮件及其附件含有龙芯中科的商业秘密信息,仅限于发送给上面地址中列
> >> 出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部
> >> 分地泄露、复制或散发)本邮件及其附件中的信息。如果您错收本邮件,请
> >> 您立即电话或邮件通知发件人并删除本邮件。
> >> This email and its attachments contain confidential information
> >> from Loongson Technology , which is intended only for the person
> >> or entity whose address is listed above. Any use of the
> >> information contained herein in any way (including, but not
> >> limited to, total or partial disclosure, reproduction or
> >> dissemination) by persons other than the intended recipient(s) is
> >> prohibited. If you receive this email in error, please notify the
> >> sender by phone or email immediately and delete it.
> 
> 
> What the hack is this? Isn't this mailing list public?

Yes those mail footers are obnoxious and incorrect and should be
yeeted into the sun, but at this point I don't think it helps anyone
bringing it up every time one appears. And the folks whose mails
include them usually have no control over it; it's forced on them
either by policy or technical measures of their mail systems. :(

Rich

  reply	other threads:[~2023-02-13 14:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 12:17 花静云
2023-02-13 14:12 ` alice
2023-02-13 14:17   ` David Wang
2023-02-13 14:26     ` Rich Felker [this message]
2023-02-13 14:23   ` Rich Felker

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=20230213142632.GS4163@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=00107082@163.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).