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

[GH-ISSUE #696] PDF last modified date #4170

New Issue
Closed
opened 2026-04-19 12:10:44 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-19 12:10:44 -05:00
Owner
Copy Link

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

Originally assigned to: @hzeljko on GitHub.

@hzeljko somewhere in the PDF, we need to have a last modified date. Not sure sure where to put it. Is there a standard place we can make a date appear?

Originally created by @profvjreddi on GitHub (Feb 7, 2025). Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/696 Originally assigned to: @hzeljko on GitHub. @hzeljko somewhere in the PDF, we need to have a last modified date. Not sure sure where to put it. Is there a standard place we can make a date appear?
GiteaMirror added the format: pdfarea: book labels 2026-04-19 12:10:44 -05:00
GiteaMirror commented 2026-04-19 12:10:46 -05:00
Author
Owner
Copy Link

@hzeljko commented on GitHub (Feb 10, 2025):

@profvjreddi The date (most often in the format: month, year) is located on the Title Page, at the very bottom.
In addition, the year of publication of the book can be found on the Copyright Page.

Image

I suggest that the TiTtile Page looks like the picture I am sending

<!-- gh-comment-id:2648355735 --> @hzeljko commented on GitHub (Feb 10, 2025): @profvjreddi The date (most often in the format: month, year) is located on the Title Page, at the very bottom. In addition, the year of publication of the book can be found on the Copyright Page. ![Image](https://github.com/user-attachments/assets/13b7995c-6705-454a-85c1-f079acf7d6d9) I suggest that the TiTtile Page looks like the picture I am sending
GiteaMirror commented 2026-04-19 12:10:47 -05:00
Author
Owner
Copy Link

@profvjreddi commented on GitHub (Feb 10, 2025):

Thanks @hzeljko that looks great.

Let's lock this in.

<!-- gh-comment-id:2648384349 --> @profvjreddi commented on GitHub (Feb 10, 2025): Thanks @hzeljko that looks great. Let's lock this in.
GiteaMirror commented 2026-04-19 12:10:47 -05:00
Author
Owner
Copy Link

@hzeljko commented on GitHub (Feb 10, 2025):

@profvjreddi
I will send an update in the next PR together with chapter 6: data_engineering.qmd

<!-- gh-comment-id:2648490524 --> @hzeljko commented on GitHub (Feb 10, 2025): @profvjreddi I will send an update in the next PR together with chapter 6: data_engineering.qmd
GiteaMirror commented 2026-04-19 12:10:49 -05:00
Author
Owner
Copy Link

@profvjreddi commented on GitHub (Feb 10, 2025):

Could you please just make it a separate PR cause I don't like to mix them
together.

Vijay Janapa Reddi, Ph. D. |
John L. Loeb Associate Professor of Engineering and Applied Sciences |
John A. Paulson School of Engineering and Applied Sciences |
Science and Engineering Complex (SEC) | 150 Western Ave, Room #5.305 |
Boston, MA 02134 |
Harvard University | My Website
http://scholar.harvard.edu/vijay-janapa-reddi | Google Scholar
https://scholar.google.com/citations?hl=en&user=gy4UVGcAAAAJ&view_op=list_works&sortby=pubdate
| Edge Computing Lab https://edge.seas.harvard.edu | Book Meeting
https://fantastical.app/vjreddi/ | Contact Admin
https://scholar.harvard.edu/vijay-janapa-reddi/contact |

On Mon, Feb 10, 2025 at 10:59 AM, Zeljko Hrcek @.***>
wrote:

@profvjreddi https://github.com/profvjreddi
I will send an update in the next PR together with chapter 6:
data_engineering.qmd

—
Reply to this email directly, view it on GitHub
https://github.com/harvard-edge/cs249r_book/issues/696#issuecomment-2648490524,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABT6DFDAAXRPXMEWUKWED7T2PDEETAVCNFSM6AAAAABWW2MDGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBYGQ4TANJSGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

<!-- gh-comment-id:2648498622 --> @profvjreddi commented on GitHub (Feb 10, 2025): Could you please just make it a separate PR cause I don't like to mix them together. Vijay Janapa Reddi, Ph. D. | John L. Loeb Associate Professor of Engineering and Applied Sciences | John A. Paulson School of Engineering and Applied Sciences | Science and Engineering Complex (SEC) | 150 Western Ave, Room #5.305 | Boston, MA 02134 | Harvard University | My Website <http://scholar.harvard.edu/vijay-janapa-reddi> | Google Scholar <https://scholar.google.com/citations?hl=en&user=gy4UVGcAAAAJ&view_op=list_works&sortby=pubdate> | Edge Computing Lab <https://edge.seas.harvard.edu> | Book Meeting <https://fantastical.app/vjreddi/> | Contact Admin <https://scholar.harvard.edu/vijay-janapa-reddi/contact> | On Mon, Feb 10, 2025 at 10:59 AM, Zeljko Hrcek ***@***.***> wrote: > @profvjreddi <https://github.com/profvjreddi> > I will send an update in the next PR together with chapter 6: > data_engineering.qmd > > — > Reply to this email directly, view it on GitHub > <https://github.com/harvard-edge/cs249r_book/issues/696#issuecomment-2648490524>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABT6DFDAAXRPXMEWUKWED7T2PDEETAVCNFSM6AAAAABWW2MDGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBYGQ4TANJSGQ> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
GiteaMirror commented 2026-04-19 12:10:50 -05:00
Author
Owner
Copy Link

@hzeljko commented on GitHub (Feb 10, 2025):

Of course. I will do it very soon.

<!-- gh-comment-id:2648536834 --> @hzeljko commented on GitHub (Feb 10, 2025): Of course. I will do it very soon.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: book
area: collabs
area: kits
area: socratiq
area: tinytorch
area: tools
area: website
bug
dependencies
format: epub
format: pdf
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 format: pdf
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#4170
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?