Author(s):	Deepa Dinamani
Location	A2
Date	jan Wed 23	Days Raw Files
Start	13:30	First Raw Start	13:05
Duration	0:45:0	Offset	0:24:29
End	14:15	Last Raw End	14:35
Chapters	00:00 0:04:51 0:34:50
Total cuts_time	43 min.

https://2019.linux.conf.au/schedule/presentation/113/
raw-playlist raw-mp4-playlist encoded-files-playlist host public tweet mp4 svg png

assets release.pdf How_the_quest_to_prevent_time_from_running_out_has_led_me_to_all_corners_of_the_Linux_kernel.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Drivers, filesystems, sockets, input events, vdso, python?? and more... Everything that needs to be fixed to prevent from time overflow. This is a talk about some of the problems I expected, and new ones I discovered, on our way to solving the 32-bit timestamps problem for the Linux Kernel. I work with Arnd Bergmann on solving the y2038 problem. I would like to paint a picture of how we see the problem: our design principles, strategies and end with where we are today. markdown
Comment:	production notes