@@ -22,10 +22,10 @@ This edition covers what happened during the months of June and July 2025.
22
22
23
23
* 20 years ago: [ Meet the new maintainer..] ( https://lore.kernel.org/git/Pine.LNX.4.58.0507262004320.3227@g5.osdl.org/ )
24
24
25
- On July 26 Jul 2005, so 20 years ago, Linus Torvalds announced on
25
+ On July 26 2005, so 20 years ago, Linus Torvalds announced on
26
26
the mailing list that Junio Hamano accepted the maintainership of
27
27
the Git project and that Junio "was the obvious choice". Linus said
28
- he wasn't dropping Git but he just prefered working on it as a
28
+ he wasn't dropping Git but he just preferred working on it as a
29
29
contributor.
30
30
31
31
Junio replied with an [ A note from the new GIT maintainer] ( https://lore.kernel.org/git/7vmzo8ss2l.fsf@assigned-by-dhcp.cox.net/ )
@@ -48,7 +48,7 @@ This edition covers what happened during the months of June and July 2025.
48
48
investigated.
49
49
50
50
[ Registration is open] ( https://events.linuxfoundation.org/open-source-summit-europe/features/co-located-events/#git-mini-summit-2025 )
51
- for only the Git Mini Summit and for the Open Source Summit Europe including the Git Mini Summit.
51
+ for both the Git Mini Summit only and for the Open Source Summit Europe including the Git Mini Summit.
52
52
53
53
54
54
### Reviews
@@ -57,11 +57,11 @@ This edition covers what happened during the months of June and July 2025.
57
57
58
58
Last April, Aditya Garg sent a patch series containing three main
59
59
changes to ` git send-email ` . He mentioned that he was sending the
60
- email series using the very patches he is proposing, via Outlook.
60
+ email series using the very patches he was proposing, via Outlook.
61
61
62
62
The first patch, which was a rebased version of
63
63
[ an earlier patch by Julian Swagemakers] ( https://lore.kernel.org/git/20250125190131.48717-1-julian@swagemakers.org/ )
64
- added support for OAuth2 authentication, which started to be
64
+ adding support for OAuth2 authentication, which started to be
65
65
required by Microsoft. Julian's patch unfortunately had been waiting
66
66
for review for over a year before Aditya picked it up.
67
67
@@ -74,7 +74,7 @@ This edition covers what happened during the months of June and July 2025.
74
74
Junio Hamano, the Git maintainer, reviewed the three patches saying
75
75
he liked the commit messages, documentation and code comments even
76
76
though he suggested a few small style improvements to the code
77
- style, and a number of grammar and formatting changes to the
77
+ style plus a number of grammar and formatting changes to the
78
78
documentation.
79
79
80
80
He also asked for reviews from others as he said he was not familiar
@@ -117,7 +117,7 @@ This edition covers what happened during the months of June and July 2025.
117
117
module was officially released with this new functionality. This
118
118
successful collaboration meant the first patch in the series, which
119
119
was a workaround for the missing library support, was no longer
120
- needed and was subsequently dropped. Instead the new version of
120
+ needed and was subsequently dropped. Instead, the new version of
121
121
` Authen::SASL ` started to benefit all Perl users.
122
122
123
123
Greg Kroah-Hartman echoed what brian had suggested about using a
@@ -145,7 +145,7 @@ This edition covers what happened during the months of June and July 2025.
145
145
### Support
146
146
-->
147
147
148
- ## Developer Spotlight: Usman Akinyemi
148
+ ## Developer Spotlight: Usman Akinyemi
149
149
150
150
_ Editor’s note: This edition features a retrospective interview with a
151
151
contributor who contributed to Git through a mentoring program. We hope
@@ -185,13 +185,13 @@ welcome your thoughts and feedback!_
185
185
project I use every time, also the thought of contributing to a
186
186
project used by almost all the developers in the whole world was
187
187
definitely a dream coming true. To also maximize my getting selected
188
- for Outreachy, I picked Git because it is written in C programming
188
+ for Outreachy, I picked Git because it is written in C,
189
189
which many other participants are always scared to pick (going for the
190
190
hard thing). The story did not end there as I got selected for both
191
191
LibreOffice and Git and I had to choose one as my Outreachy projects.
192
192
It was a hard decision but I picked it mainly because the Git
193
193
community is a community where it is so easy to communicate with other
194
- team members, it is a community where I clearly know who is who and
194
+ team members, and it is a community where I clearly know who is who and
195
195
what they do in the community. Also Git is more well recognised.
196
196
197
197
* ** How do you feel your contribution has impacted the Git community
@@ -250,19 +250,19 @@ welcome your thoughts and feedback!_
250
250
251
251
Technically, I have been able to improve my C programming and bash
252
252
scripting skills. Also reading and understanding very large codebases
253
- like Git. Of course now, I can call myself an expert in using Git as a
253
+ like Git. Of course now I can call myself an expert in using Git as a
254
254
tool itself.
255
255
256
- To contribute to Git, you must be able to communicate well as all the
256
+ To contribute to Git, you must be able to communicate well, as all the
257
257
Git workflows happen remotely and over mailing lists. Most of the time
258
- in the Git community, it is not about the correctness of your code, it
258
+ in the Git community it is not about the correctness of your code -- it
259
259
is about how well you can communicate your rationale to the community
260
260
before your patches can be accepted. So, over time, as a Git
261
261
contributor, my communication skills in a technical environment have
262
262
really improved.
263
263
264
264
I have also learnt to write clean code, organize my changes into well
265
- formatted patches and write clear commit messages.
265
+ formatted patches, and write clear commit messages.
266
266
267
267
* ** What was your biggest takeaway or learning from Outreachy that
268
268
you now apply regularly in your work?**
@@ -285,10 +285,10 @@ welcome your thoughts and feedback!_
285
285
that Git does not use GitHub or GitLab, something someone would have
286
286
thought they will be using. Git uses a mailing list just like the
287
287
Linux kernel. While writing this, I remember that I had a challenge
288
- retrieving patches from the mailing list as my project depends on some
288
+ retrieving patches from the mailing list as my project depended on some
289
289
patches that were sent by my mentor previously. I had to use ` git am ` ,
290
- something I never used before. Help from my mentor really helped
291
- and reading through the the "[ Hacking Git] ( https://git.github.io/Hacking-Git/ ) "
290
+ something I never used before. Help from my mentor really helped,
291
+ as well as reading through the "[ Hacking Git] ( https://git.github.io/Hacking-Git/ ) "
292
292
page.
293
293
294
294
* ** Have you thought about mentoring new GSoC / Outreachy students?**
@@ -303,8 +303,8 @@ welcome your thoughts and feedback!_
303
303
Smile, I will definitely say the Rustication of some parts of Git
304
304
which has been going on currently, I think one that has already been
305
305
integrated to Git is [ libgit-rs] ( https://lore.kernel.org/git/cover.1738187176.git.steadmon@google.com/ ) .
306
- Rust seems to be a language that focuses more on safety/security
307
- and safety/security in Git is very important. I am also a Rustacean
306
+ Rust seems to be a language that focuses more on safety/security,
307
+ and safety/security is very important in Git . I am also a Rustacean
308
308
so I should be able to help hopefully if that happens.
309
309
310
310
* ** If you could remove something from Git without worrying about
@@ -324,7 +324,7 @@ welcome your thoughts and feedback!_
324
324
* ** What is your favorite Git-related tool/library, outside of Git
325
325
itself?**
326
326
327
- I think is GitHub and GitLab, if I have to choose one, I will say GitHub.
327
+ I think it's both GitHub and GitLab -- if I have to choose one, I will say GitHub.
328
328
329
329
* ** What is your toolbox for interacting with the mailing list and for
330
330
development of Git?**
@@ -333,7 +333,7 @@ welcome your thoughts and feedback!_
333
333
just to get my patches to the mailing list faster but, along the line
334
334
I switched to ` git send-email ` and really, it is more flexible and easy
335
335
to use than I thought of it. For my machine, I basically use Arch Linux
336
- and Neovim for my text editor.
336
+ and Neovim as my text editor.
337
337
338
338
* ** How do you envision your own involvement with Git or other open
339
339
source projects in the future?**
@@ -343,8 +343,8 @@ welcome your thoughts and feedback!_
343
343
and even making some few bucks through internships. After my
344
344
internship at Outreachy, I did send patches to the Git community and I
345
345
planned to keep doing that. After Outreachy, I have contributed to a
346
- few other projects like RISCV and OSIPI (through GSoC). I currently
347
- mentor people who want to start their open source journey and I plan
346
+ few other projects like RISC-V and OSIPI (through GSoC). I currently
347
+ mentor people who want to start their open source journey, and I plan
348
348
to do more of it. I planned to keep contributing to open source
349
349
projects and hopefully get a job in open source.
350
350
0 commit comments