Skip to content

Added 2026/04/2026-04-01-unisoc.md#20156

Merged
dmca-sync-bot merged 1 commit intomasterfrom
updates
Apr 2, 2026
Merged

Added 2026/04/2026-04-01-unisoc.md#20156
dmca-sync-bot merged 1 commit intomasterfrom
updates

Conversation

@dmca-sync-bot
Copy link
Copy Markdown
Collaborator

This is an automated pull request to sync changes from upstream repository.

Diff summary:

A 2026/04/2026-04-01-unisoc.md

Copilot AI review requested due to automatic review settings April 2, 2026 17:58
@dmca-sync-bot dmca-sync-bot merged commit af43ded into master Apr 2, 2026
@dmca-sync-bot dmca-sync-bot deleted the updates branch April 2, 2026 17:59
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new DMCA takedown notice document for UNISOC dated 2026-04-01, synced from an upstream source.

Changes:

  • Added a new markdown notice file under 2026/04/ documenting UNISOC’s claim regarding an allegedly infringing repository.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +1 to +7
Dear GitHub Legal Team,



I am [private], a member of the [private] department of UNISOC Technologies Co.,Ltd (“UNISOC”).

I have read and understood GitHub's "DMCA Notice Submission Guidelines"
Copy link

Copilot AI Apr 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This notice starts directly with the submitter’s letter and doesn’t include the standard GitHub annotation header + README link + --- divider that appears on some notices when repo owners were given time to make changes (see README.md “Anatomy of a takedown notice”, and e.g. 2026/01/2026-01-07-unisoc.md lines 1–8). Worth double-checking whether that annotation is intentionally omitted for this notice, or if it was accidentally dropped during the upstream sync.

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants