-
Notifications
You must be signed in to change notification settings - Fork 1.3k
pls delete this
#11391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
pls delete this
#11391
Conversation
Added 2022/06/2022-06-02-ar-foundation-editor-remote-3.md
Added 2022/06/2022-06-02-gisaid-2.md
Added 2022/06/2022-06-02-ar-foundation-editor-remote-4.md
Modified 2022/06/2022-06-01-wiley.md
Added 2022/06/2022-06-02-ar-foundation-editor-remote-5.md
Added 2022/06/2022-06-02-ar-foundation-editor-remote-6.md
Added 2022/06/2022-06-02-sensetime.md
Added 2022/06/2022-06-02-sensetime-2.md
Added 2022/06/2022-06-02-isoftstone.md
Added 2022/06/2022-06-03-rivierawaves.md
Added 2022/06/2022-06-06-whmcs.md
Added 2022/06/2022-06-06-cchosting.md
Added 2022/06/2022-06-03-stereoarts-5.md
Added 2022/06/2022-06-03-stereoarts-4.md
Added 2022/06/2022-06-06-okok.md
Added 2022/06/2022-06-17-imoshield.md
Added 2022/06/2022-06-17-usc.md
Added 2022/06/2022-06-17-wiley.md
Added 2022/06/2022-06-20-acs-hms-pro.md
Added 2022/06/2022-06-20-product-source-code.md
sorry i deleted my comment because I was on the wrong page. Sorry! |
ok |
66324cf
to
14285da
Compare
what? is this just because of a youtuber? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
আমার পেজে সমসা হইছে প্লিজ কমেন্ট করুন
বেশি বেশি
আবারো প্লিজ
what is wrong with this repo 💀💀 |
I don't use this repo anymore |
LGTM |
Shut up |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fuck the DMCA and fuck microsoft
DMCA is quite handy actualy, it also helps small authors protect their own
work,
but i agree fuck microsoft
Op ma 14 jul 2025 om 12:28 schreef Salih Muhammed ***@***.***
…:
***@***.**** requested changes on this pull request.
Fuck the DMCA and fuck microsoft
—
Reply to this email directly, view it on GitHub
<#11391 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A27ESLM3Q3D4UET3WBUKPWT3IOA55AVCNFSM6AAAAABVIWIBM2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTAMJVG42TINRQHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
FUCK MICROSOFT YEAAHHHH!!!!!!!!!!!!!! |
If you are looking to file or dispute a takedown notice by posting to this repository, please STOP 🛑 because we do not accept Pull Requests or other contributions to this repository.
Read on to learn about the available paths forward.
Please note that re-posting the exact same content that was the subject of a takedown notice without following the proper process (outlined below) is a violation of GitHub’s DMCA Policy and Terms of Service. If you commit or post content to this repository that violates our Terms of Service, we will delete that content and may suspend access to your account as well.
Submitting a DMCA Notice
If you are a copyright owner wishing to submit a takedown notice, read our DMCA Policy and Guide to Submitting a DMCA Takedown Notice. You can submit the actual notice using our special Copyright Claims Contact Form.
Responding to a DMCA Notice
If you are the owner of a repository that has been taken down, you have two main options:
Do you want to make changes to the repository that would remove the allegedly infringing content? If that is possible in your case, contact us to let us know that you would like to make the changes.
Do you want to formally dispute the action by submitting a counter notice? Maybe the person sending the takedown notice does not hold the copyright or did not realize that you have a license or made some other mistake in their takedown notice. If you believe your content on GitHub was mistakenly disabled by a DMCA takedown request, you have the right to contest the takedown by submitting a counter notice. If you do, we will wait 10-14 days and then re-enable your content unless the copyright owner initiates a legal action before then.
If you do not want to make changes or dispute the notice, but still have general concerns about the copyright laws and how they apply in your case, know that GitHub and developers have the opportunity and a voice to advocate for changes in law and public policy to better support software development. We are constantly looking to advocate for developers, so feel free to reach out and let us know your concerns. We also encourage you to learn more about copyright and speak up by reaching out to the Copyright Office or your local lawmakers to voice your concerns.