[ot][journal][personal][crazy] trying to write something clearer :)
i've been acting crazy for over a decade now. when i realize how old i am, forming new experiences so poorly, it can be scary. [it's okay to keep going or to change the topic. finding simple more relaxing thoughts that are near other thoughts might help.]
one of the things i enjoy nowadays is submitting patches on github and waiting to get a reply (or fork the repository if i have the gusto! an open sourcer recommended that to me.). the dopamine drop of having your contribution merged in seems similar to buying a small new product after joining capitalism. i might guess i submit about a patch a week, might be an overestimate maybe a [--scared re joining-capitalism-expression]
[censored??] -- all on github for now. my last patch was https://github.com/5afe/pysha3/pull/3 but it's unlikely to be accepted because i have not tested it. [prior to this i participated more on wheecode/mecode and have commit access to jminardi's mecode repository, some strange things] -- a fun thing about mecode/wheecode is that, after handling so many "fork/mergeh hells", i wrote my first script to automatically migrate commits from one repository to another, by renaming the folder and presenting the user with a rebase. maybe the most interesting part of that [script to me is the git plumbing command for making a handmade commit object]
script visible at https://github.com/xloem/wheecode/commit/a21120eae018a12d4161991946d57a0a530... it's just quick pasta the three lines of interest are 85, 99, and 114 here are lines 85 and 99: 85: transform=--path-rename="$srcname":"$dstname" 99: git filter-repo $transform --source "$SRC_REPO" --target "$DST_REPO" --refs "$SRCTIP" --replace-refs update-and-add i don't like sharing these two lines but they happen prior to the next one. git-filter-repo is an evil bookburning tool for changing the entirety of git history such that something was different. in the world wide web i see, it seems presently recommended by the git project over git-filter-branch and such. i rename a subfolder into a new repository and then rebase only the commits of interest. here's line 114: 114: MERGE_COMMIT="$(git commit-tree -m "Rebased and merged $1 from $srcname into $dstname." "$DST_TREE" -p "$DSTTIP" -p "$SRCTIP")" git commit-tree is a really cool plumbing command for creating a manual commit. of course, it would be nice if git-merge let you make arbitrary merge commits itself (it only merges the working tree) but as a nerd i find internals pretty fun when i have time to engage them. -m gives the message for the new commit, the positional parameter is the tree associated with the commit (which I got with `git rev-parse HEAD^{tree}` where ^{tree} is a magic git suffix that means the tree rather than the commit) and each -p is a parent for the commit. the new commit hash is output on stdout.
reviewing it i’m seeing i could have used git-merge within the temporary repository and not used git-commit-tree. i probably didn’t do that to make it easier to break the problem into simple steps with parts that were easier to remember near each other. briefly wondering whether it’s memory or whether it’s part of my thinking influencing other parts of my thinking. either way, coping strategies for holding things as cognitively simple conceptual parts.
[so i was all "who is adam back that profrat keeps mentioning" and turns out adam is a famous dev who identifies as a cypherpunk and it really is decades in the future and cypherpunks are a famous hacker movement ... one thing i noticed is that antiforensics is topical. i have lots of thoughts near antiforensics! when i started losing it one of my behaviors was extensive brainstorming on extracting profiles from low-density information (puzzles that don't scare imaginary mcboss)]
participants (1)
-
Undescribed Horrific Abuse, One Victim & Survivor of Many