github-starred/cs249r_book
2
0
Fork 0
mirror of https://github.com/harvard-edge/cs249r_book.git synced 2026-05-22 14:03:46 -05:00
Code Issues 114 Packages Projects Releases 24 Wiki Activity

[GH-ISSUE #22] Re-structure chapters -> folders #1223

New Issue
Closed
opened 2026-04-11 07:39:01 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-11 07:39:01 -05:00
Owner
Copy Link

Originally created by @profvjreddi on GitHub (Oct 7, 2023).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/22

Originally assigned to: @Naeemkh on GitHub.

Need to structure each chapter QMD file as a folder so that we can keep the (1) content and (2) exercises together.

Originally created by @profvjreddi on GitHub (Oct 7, 2023). Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/22 Originally assigned to: @Naeemkh on GitHub. Need to structure each chapter QMD file as a folder so that we can keep the (1) content and (2) exercises together.
GiteaMirror added the area: bookarea: tools labels 2026-04-11 07:39:01 -05:00
GiteaMirror commented 2026-04-11 07:39:03 -05:00
Author
Owner
Copy Link

@V0XNIHILI commented on GitHub (Dec 10, 2023):

You are working on this right now, right?

<!-- gh-comment-id:1849065553 --> @V0XNIHILI commented on GitHub (Dec 10, 2023): You are working on this right now, right?
GiteaMirror commented 2026-04-11 07:39:03 -05:00
Author
Owner
Copy Link

@V0XNIHILI commented on GitHub (Dec 10, 2023):

I think we should not leave mvfiles.py is the project.

<!-- gh-comment-id:1849066035 --> @V0XNIHILI commented on GitHub (Dec 10, 2023): I think we should not leave [`mvfiles.py`](https://github.com/harvard-edge/cs249r_book/blob/main/mvfiles.py) is the project.
GiteaMirror commented 2026-04-11 07:39:04 -05:00
Author
Owner
Copy Link

@profvjreddi commented on GitHub (Dec 10, 2023):

I agree @V0XNIHILI - I was in the midst of cleaning it up!

I finished this with @Naeemkh's help on how to structure things. The commit responsible for this is 3625af9cc4 🥳

<!-- gh-comment-id:1849078254 --> @profvjreddi commented on GitHub (Dec 10, 2023): I agree @V0XNIHILI - I was in the midst of cleaning it up! I finished this with @Naeemkh's help on how to structure things. The commit responsible for this is 3625af9cc4bfbc5e4f6e1eb9272b11d008825164 🥳
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: 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 area: book area: tools
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#1223
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?