kjodle/the-codex
kjodle/the-codex
1
1
Fork 0
Code Issues 2 Pull Requests Projects Releases 2 Wiki Activity

Additions to coda regarding new organization

Browse Source
This commit is contained in:
Kenneth John Odle 2025-02-13 08:58:54 -05:00
parent c2e4bb3e8a
commit 546c23044b
2 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
006/006 time.csv
View File

@ -31,3 +31,5 @@ Date,Topic,Minutes
,aside on memorization,30
,(ch. 1 - supporting open source),50
2025.02.10,ch. 2 edits & corrections,30
2025.02.12,ch. 2 proofreading,16
2025.02.13,additions to coda,15

1 Issue #6
31 ,(ch. 1 - supporting open source),50
32 2025.02.10,ch. 2 edits & corrections,30
33 2025.02.12,ch. 2 proofreading,16
34 2025.02.13,additions to coda,15
35

4
006/include/coda.tex
View File

@ -27,7 +27,9 @@ For this issue, I decided to write up each chapter as a separate file, and then
\begin{multicols}{2}
\begin{small}
\noindent{}First paragraph.
\noindent{}This is the sixth issue of this zine. I originally did this so I could learn how to use \LaTeX{} and also learn more about Linux. I thought I might get one or two issues and that would be the end of it. So when I started doing this, I pushed everything to my git repo at \kref{https://git.kjodle.net/kjodle/the-codex}{https://git.kjodle.net/kjodle/the\\-codex}.
It looks like this is a thing now, and a single repo just won't work. I'm just over 300 commits in that repo, which doesn't really reveal much about the state of each issue. So, going forward, I'm going to be making commits to a different project on my git repo at \kref{https://git.kjodle.net/the-codex-zine}{https://git.kjodle.net/the-codex-\\zine}. That way, each issue can have its own repository and will eventually come to a logical end, instead of being never ending.
\medskip
\begin{flushright}