Junio Hamano, the Git maintainer, sent a to the mailing list
29
-
which updated the ReviewingGuidelines.txt documentation with the
29
+
which updated the 'ReviewingGuidelines.txt' documentation with the
30
30
goal of encouraging positive reviews even more.
31
31
32
-
The ReviewingGuidelines.txt documentation was
32
+
The 'ReviewingGuidelines.txt' documentation was
33
33
[created a few years ago](https://lore.kernel.org/git/[email protected]/)
34
34
by Victoria Dye to provide "consistent definitions for common
35
35
review terminology" and to give advice to reviewers, in a similar
@@ -98,15 +98,15 @@ __Various__
98
98
you can find the interview with Jakub Narębski in [Edition #17](https://git..io/rev_news/2016/07/20/edition-17/).
99
99
100
100
__Light reading__
101
-
+[Different ways to use “--” in Git](https://tekin.co.uk/2024/08/the-many-uses-for-git-)
101
+
+[Different ways to use `--` in Git](https://tekin.co.uk/2024/08/the-many-uses-for-git-)
102
102
by Tekin Süleyman on his blog. It describes selectively stashing changes,
103
103
selectively discarding changes, and selectively restoring changes.
104
104
This article expands on the
105
-
"[interactively stage changes with --](https://tekin.co.uk/2017/03/git-tips-you-possibly-did-not-know-you-needed#3-interactively-stage-changes-with---)" advice
105
+
"[interactively stage changes with \-\-](https://tekin.co.uk/2017/03/git-tips-you-possibly-did-not-know-you-needed#3-interactively-stage-changes-with---)" advice
106
106
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).
107
107
+[Tracing the evolution of a Python function with git log](https://nerderati.com/tracing-the-evolution-of-a-python-function-with-git-log/)
108
108
by Joël Perras on his Nerderati blog. It shows a detailed example on using `git log -L`
109
-
(and `diff=python` gitattribute) to diagnose a real-life bug that was ostensibly
109
+
(and the `diff=python` gitattribute) to diagnose a real-life bug that was ostensibly
110
110
caused by an upgrade to Authlib.
111
111
+ This technique is also described in the
112
112
[See the History of a Method with `git log -L`](https://calebhearth.com/git-method-history) article,
@@ -121,17 +121,17 @@ __Light reading__
121
121
+[Back-dating Git commits based on file modification dates](https://til.simonwillison.net/git/backdate-git-commits)
122
122
by Simon Willison in his [TILs on Git](https://til.simonwillison.net/git)
123
123
(Today I’ve Learned).
124
-
+ It was used by the author to create [1991-WWW-NeXT-Implementation](https://.com/simonw/1991-WWW-NeXT-Implementation)
124
+
+ It was used by the author to create the [1991-WWW-NeXT-Implementation](https://.com/simonw/1991-WWW-NeXT-Implementation)
125
125
repository out of [the archive](https://www.w3.org/History/1991-WWW-NeXT/Implementation/)
126
126
of Tim Berner-Lee's original code for the WorldWideWeb application for NeXT.
127
127
This endeavor was described in a short blog post, [1991-WWW-NeXT-Implementation on ](https://simonwillison.net/2024/Aug/1/www-next-implementation-on-/).
128
128
+[Store Code Discussions in Git using Git Notes](https://wouterj.nl/2024/08/git-notes)
129
129
by Wouter de Jong on his blog. The article includes some code (in PHP)
130
130
that uses the API to fetch the pull request comments and store them
131
-
in notes (under `-comments` notes reference).
131
+
in notes (under the `-comments` notes reference).
132
132
+[Attaching notes to git branches](https://dev.to/pinotattari/attaching-notes-to-git-branches-503k)
133
-
by Riccardo Bernardini on DEV\.to. The article describes why this feature is useful,
134
-
and how `git branch --edit-description` and `git notes` fall short; which led to
133
+
by Riccardo Bernardini on DEV\.to. The article describes why this feature is useful
134
+
and how `git branch --edit-description` and `git notes` fall short; this led to
135
135
the creation of the [git-branchnotes](https://gitlab.com/mockturtle/git-branchnotes) tool.
136
136
+[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)
137
137
by Bill Harding (CEO at GitClear) on StackOverflow Blog.
@@ -142,14 +142,14 @@ __Light reading__
142
142
is not the only one available in [`git diff`](https://git-scm.com/docs/git-diff):
143
143
there are also `minimal`, `patience` and `histogram` diff algorithms available
144
144
(via the `--diff-algorithm` option);
145
-
this was not stated in the article.
145
+
this is not stated in the article.
146
146
+[How Different Are Different diff Algorithms in Git?](https://cs.paperswithcode.com/paper/how-different-are-different-diff-algorithms):
147
147
a paper with code by Yusuf Sulistyo Nugroho, Hideaki Hata, Kenichi Matsumoto
148
148
from 2019.
149
149
+[Git Things: A grab bag of less frequently talked about git adjacent points](https://matklad..io/2023/12/31/git-things.html)
150
150
by Alex Kladov (matklad) on his Pages-based blog, from 2023.
151
151
+[Unified Versus Split Diff](https://matklad..io/2023/10/23/unified-vs-split-diff.html):
152
-
for code reviews (and what the author uses)
152
+
a discussion what is better for code reviews (and what the author uses)
153
153
by Alex Kladov (matklad) on his Pages-based blog, from 2023.
154
154
+[How Does Git Store Files?](https://blog.git-init.com/how-does-git-store-files/)
155
155
— from a conceptual point of view. An article by by Alexis Määttä Vinkler
0 commit comments