github-starred/cs249r_book
2
0
Fork 0
mirror of https://github.com/harvard-edge/cs249r_book.git synced 2026-07-16 06:07:17 -05:00
Code Issues 276 Packages Projects Releases 26 Wiki Activity

[PR #399] [MERGED] Edit privacy security #32417

New Issue
Closed
opened 2026-07-13 11:10:51 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-07-13 11:10:51 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/harvard-edge/cs249r_book/pull/399
Author: @Sara-Khosravi
Created: 8/25/2024
Status: ✅ Merged
Merged: 8/26/2024
Merged by: @profvjreddi

Base: dev ← Head: edit-privacy-security

📝 Commits (3)

📊 Changes

1 file changed (+10 additions, -10 deletions)

View changed files

📝 contents/privacy_security/privacy_security.qmd (+10 -10)

📄 Description

Before submitting your Pull Request, please ensure that you have carefully reviewed and completed all items on this checklist.

  1. Content

    • The chapter content is complete and covers the topic in detail.
    • All technical terms are well-defined and explained.
    • Any code snippets or algorithms are well-documented and tested.
    • The chapter follows a logical flow and structure.

  2. References & Citations

    • All references are correctly listed at the end of the chapter.
    • In-text citations are used appropriately and match the references.
    • All figures, tables, and images have proper sources and are cited correctly.

  3. Quarto Website Rendering

    • The chapter has been locally built and tested using Quarto.
    • All images, figures, and tables render properly without any glitches.
    • All images have a source or they are properly linked to external sites.
    • Any interactive elements or widgets work as intended.
    • The chapter's formatting is consistent with the rest of the book.

  4. Grammar & Style

    • The chapter has been proofread for grammar and spelling errors.
    • The writing style is consistent with the rest of the book.
    • Any jargon is clearly explained or avoided where possible.

  5. Collaboration

    • All group members have reviewed and approved the chapter.
    • Any feedback from previous reviews or discussions has been addressed.

  6. Miscellaneous

    • All external links (if any) are working and lead to the intended destinations.
    • If datasets or external resources are used, they are properly credited and linked.
    • Any necessary permissions for reused content have been obtained.

  7. Final Steps

    • The chapter is pushed to the correct branch on the repository.
    • The Pull Request is made with a clear title and description.
    • The Pull Request includes any necessary labels or tags.
    • The Pull Request mentions any stakeholders or reviewers who should take a look.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/harvard-edge/cs249r_book/pull/399 **Author:** [@Sara-Khosravi](https://github.com/Sara-Khosravi) **Created:** 8/25/2024 **Status:** ✅ Merged **Merged:** 8/26/2024 **Merged by:** [@profvjreddi](https://github.com/profvjreddi) **Base:** `dev` ← **Head:** `edit-privacy-security` --- ### 📝 Commits (3) - [`0bf86b9`](https://github.com/harvard-edge/cs249r_book/commit/0bf86b9b113e6cb9d95b3787474f87e0758a124a) Edit Power Attack and Side-Channel Attack sections - [`6cd3bb4`](https://github.com/harvard-edge/cs249r_book/commit/6cd3bb41c2f961203b6ac72b26d83ce25a4cc284) Merge branch 'edit-privacy-security' of https://github.com/Sara-Khosravi/cs249r_book into edit-privacy-security - [`b6933ef`](https://github.com/harvard-edge/cs249r_book/commit/b6933ef4e998005e92ee55fedb5010d03005fa36) Merge branch 'dev' into edit-privacy-security ### 📊 Changes **1 file changed** (+10 additions, -10 deletions) <details> <summary>View changed files</summary> 📝 `contents/privacy_security/privacy_security.qmd` (+10 -10) </details> ### 📄 Description Before submitting your Pull Request, please ensure that you have carefully reviewed and completed all items on this checklist. 1. **Content** - [ ] The chapter content is complete and covers the topic in detail. - [ ] All technical terms are well-defined and explained. - [ ] Any code snippets or algorithms are well-documented and tested. - [ ] The chapter follows a logical flow and structure. 2. **References & Citations** - [ ] All references are correctly listed at the end of the chapter. - [ ] In-text citations are used appropriately and match the references. - [ ] All figures, tables, and images have proper sources and are cited correctly. 3. **Quarto Website Rendering** - [ ] The chapter has been locally built and tested using Quarto. - [ ] All images, figures, and tables render properly without any glitches. - [ ] All images have a source or they are properly linked to external sites. - [ ] Any interactive elements or widgets work as intended. - [ ] The chapter's formatting is consistent with the rest of the book. 4. **Grammar & Style** - [ ] The chapter has been proofread for grammar and spelling errors. - [ ] The writing style is consistent with the rest of the book. - [ ] Any jargon is clearly explained or avoided where possible. 5. **Collaboration** - [ ] All group members have reviewed and approved the chapter. - [ ] Any feedback from previous reviews or discussions has been addressed. 6. **Miscellaneous** - [ ] All external links (if any) are working and lead to the intended destinations. - [ ] If datasets or external resources are used, they are properly credited and linked. - [ ] Any necessary permissions for reused content have been obtained. 7. **Final Steps** - [ ] The chapter is pushed to the correct branch on the repository. - [ ] The Pull Request is made with a clear title and description. - [ ] The Pull Request includes any necessary labels or tags. - [ ] The Pull Request mentions any stakeholders or reviewers who should take a look. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-07-13 11:10:51 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: book
area: collabs
area: kits
area: labs
area: socratiq
area: staffml
area: tinytorch
area: tools
area: website
bug
dependencies
format: epub
format: pdf
javascript
link-health
link-rot
priority-high
pull-request
Mirrored from GitHub Pull Request
 staffml
type: bug
type: citation
type: code
type: errata
type: improvement
type: new
type: question
vault-sli
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/cs249r_book#32417
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?