rn-114: Add links to various news, articles, sites, and tools

Author: jnareb

rev_news/drafts/edition-114.md

@@ -82,16 +82,118 @@ This edition covers what happened during the months of July 2024 and August 2024
 ## Other News
 
 __Various__
-
++ [GitLab now supports SHA256 repositories](https://about.gitlab.com/blog/2024/08/19/gitlab-now-supports-sha256-repositories/)
+  by John Cai on GitLab Blog (in Bulletin Board category).
++ [Forgejo v8.0 is available](https://forgejo.org/2024-07-release-v8-0/).
+    + [Forgejo](https://forgejo.org/) is a self-hosted lightweight software forge,
+      written in Go; nowadays a hard fork of Gitea (which in turn was based on Gogs).
+      It was mentioned in passing in [Git Rev News Edition #103](https://git.github.io/rev_news/2023/09/30/edition-103/),
+      as one of forges working on implementing [ForgeFed](https://forgefed.org/)
+      federation protocol for forge services.
 
 __Light reading__
++ [Different ways to use “--patch” in Git](https://tekin.co.uk/2024/08/the-many-uses-for-git-patch)
+  by Tekin Süleyman on his blog.  It describes selectively stashing changes,
+  selectively discarding changes, and selectively restoring changes.
+  This article expands on the
+  "[interactively stage changes with --patch](https://tekin.co.uk/2017/03/git-tips-you-possibly-did-not-know-you-needed#3-interactively-stage-changes-with---patch)" advice
+  in [Git Tips you (Possibly) Didn't Know You Needed](https://tekin.co.uk/2017/03/git-tips-you-possibly-did-not-know-you-needed).
++ [Tracing the evolution of a Python function with git log](https://nerderati.com/tracing-the-evolution-of-a-python-function-with-git-log/)
+  by Joël Perras on his Nerderati blog.  It shows detailed example on using `git log -L`
+  (and `diff=python` gitattribute) to diagnose a real-life bug that was ostensibly
+  caused by an upgrade to Authlib.
+    + This technique is also described in the
+      [See the History of a Method with `git log -L`](https://calebhearth.com/git-method-history) article,
+      mentioned in [Git Rev News Edition #105](https://git.github.io/rev_news/2023/11/30/edition-105/).
++ [Optimize your workflow with Git stash](https://developer.mozilla.org/en-US/blog/optimize-your-workflow-git-stash/)
+  by Toon Claes (from GitLab) at MDN Blog.
++ [Seriously, You Need to Learn Git](https://blog.derlin.ch/seriously-you-need-to-learn-git)
+  by Lucy Linder on her blog (also available [on DEV\.to](https://dev.to/derlin/seriously-you-need-to-learn-git-1n8j)).  The article defines various levels of Git knowledge,
+  and explains how knowing Git might improve one's development process.
++ [Back-dating Git commits based on file modification dates](https://til.simonwillison.net/git/backdate-git-commits)
+  by Simon Willison in his [TILs on Git](https://til.simonwillison.net/git)
+  (Today I’ve Learned).
+    + It was used by the author to create [1991-WWW-NeXT-Implementation](https://github.com/simonw/1991-WWW-NeXT-Implementation)
+      repository out of [the archive](https://www.w3.org/History/1991-WWW-NeXT/Implementation/)
+      of Tim Berner-Lee's original code for the WorldWideWeb application for NeXT.
+      This endeavor was described in [1991-WWW-NeXT-Implementation on GitHub](https://simonwillison.net/2024/Aug/1/www-next-implementation-on-github/)
+      short blog post.
++ [Store Code Discussions in Git using Git Notes](https://wouterj.nl/2024/08/git-notes)
+  by Wouter de Jong on his blog.  The article includes some code (in PHP)
+  that uses the GitHub API to fetch the pull request comments and store them
+  in notes (under `github-comments` notes reference).
++ [Attaching notes to git branches](https://dev.to/pinotattari/attaching-notes-to-git-branches-503k)
+  by Riccardo Bernardini on DEV\.to.  The article describes why this feature is useful,
+  and how `git branch --edit-description` and `git notes` fall short; which led to
+  creation of [git-branchnotes](https://gitlab.com/mockturtle/git-branchnotes) tool.
++ [This developer tool is 40 years old: can it be improved?](https://stackoverflow.blog/2024/08/05/this-developer-tool-is-40-years-old-can-it-be-improved)
+  by Bill Harding (CEO at GitClear) on StackOverflow Blog.
+  The article describes how GitClear's "Commit Cruncher" diff algorithm works,
+  which was created with the goal of making code reviews easier.
+  Note that Myers diff algorithm (created by Eugene Myers in his
+  [seminal work](http://www.xmailserver.org/diff2.pdf) in 1986)
+  is not the only one available in [`git diff`](https://git-scm.com/docs/git-diff):
+  there are also `minimal`, `patience` and `histogram` diff algoritms available
+  (via the `--diff-algorithm` option);
+  this was not stated in the article.
++ [How Different Are Different diff Algorithms in Git?](https://cs.paperswithcode.com/paper/how-different-are-different-diff-algorithms):
+  a paper with code by Yusuf Sulistyo Nugroho, Hideaki Hata, Kenichi Matsumoto
+  from 2019.
++ [Git Things: A grab bag of less frequently talked about git adjacent points](https://matklad.github.io/2023/12/31/git-things.html)
+  by Alex Kladov (matklad) on his GitHub Pages-based blog, from 2023.
++ [Unified Versus Split Diff](https://matklad.github.io/2023/10/23/unified-vs-split-diff.html):
+  for code reviews (and what the author uses)
+  by Alex Kladov (matklad) on his GitHub Pages-based blog, from 2023.
++ [How Does Git Store Files?](https://blog.git-init.com/how-does-git-store-files/)
+  — from a conceptual point of view.  An article by by Alexis Määttä Vinkler
+  on [The Pragmatic Git](https://blog.git-init.com/) blog, from 2023.
+
+<!-- -->
+
++ [Code review antipatterns](https://www.chiark.greenend.org.uk/~sgtatham/quasiblog/code-review-antipatterns/)
+  for dark side developers, a joke article by Simon Tatham
+  (don’t do things described in this article).
 
 <!---
 __Easy watching__
 -->
 
 __Git tools and sites__
-
++ [The Pragmatic Git](https://blog.git-init.com/) blog;
+  note that some articles are paid members only.  Powered by Ghost.
++ [Carapace-bin](https://github.com/carapace-sh/carapace-bin) provides argument completion
+  for multiple CLI commands ([full list](https://carapace-sh.github.io/carapace-bin/completers.html)
+  includes Git, [git-extras](https://github.com/tj/git-extras), `gh` GitHub CLI, `glab` GitLab CLI,
+  `tea` Gitea CLI, etc.), and works across multiple POSIX and non-POSIX shells.
+  Details about complete support for Git can be found in issue [#99](https://github.com/carapace-sh/carapace-bin/issues/99).
+  Written in Go, under MIT license.<br>
+  Carapace-bin is a part of [Carapace](https://carapace.sh/) multi-shell completion library and binary.
+  A high-level overview of carapace itself is available at <https://pixi.carapace.sh>.
++ [git-random](https://git-random.olets.dev/): quickly build random-content Git
+  graphs with a specified shape.
+  It is a tool that can work as an aid for learning and experimenting with Git.
+  Source code available [on GitHub](https://github.com/olets/git-random/).
+  Written as single-file Bash script, under custom
+  CC BY-NC-SA 4.0 license with Hippocratic License v3 ethical requirements.
+    + The author mentions that this tool was inspired by seeing Lorna Jane Mitchell
+      use Matthew J. McCullough's [generaterandomchanges](https://github.com/matthewmccullough/scripts/blob/master/generaterandomchanges)
+      in her talk _"[Advanced Git for Developers](https://www.youtube.com/watch?v=duqBHik7nRo)"_
+      at Laracon EU 2015.
++ [git-branchnotes](https://gitlab.com/mockturtle/git-branchnotes) is a command-line tool
+  (that can be run as a git external command) that allows you to add notes to a branch and manage them.
+  Written in Ruby.
+
++ [w2vgrep - Semantic Grep](https://github.com/arunsupe/semantic-grep)
+  is a command-line tool, with the interface similar to that of `grep`,
+  that performs semantic searches on text input using word embeddings (word2vec).
+  It's designed to find semantically similar matches to the query,
+  going beyond simple string matching.  Supports multiple languages.
+  Written in Go, uses MIT license.
++ [Collective Code Construction Contract](https://rfc.zeromq.org/spec/42/) (C4)
+  is an evolution of the github.com [Fork + Pull Model](https://help.github.com/articles/about-pull-requests/),
+  aimed at providing an optimal collaboration model for free software projects.
+    + Compare with [Ship / Show / Ask: A modern branching strategy](https://martinfowler.com/articles/ship-show-ask.html) model,
+      mentioned in [Git Rev News #79](https://git.github.io/rev_news/2021/09/30/edition-79/).
 
 ## Releases