Any comment about upcoming Git Rev News edition 75

[chriscool]

A currently mostly empty draft is there:

https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-75.md

Feel free to comment in this issue, suggest topics, suggest persons to interview, or use the edit button (that looks like a pen) to edit and create a pull request with the changes you would like.

Let's try to publish this edition on Wednesday May 26th 2021!

Thanks!

cc @jnareb @mjaix @sivaraam @gitster

[chriscool]

In a comment on the issue for the previous edition @jnareb suggested covering "what at first glance looks like yet another iteration of email vs web-based workflows discussion": Pain points in Git's patch flow

[jnareb]

Should we write about issue with Freenode (where #git IRC channel is) in Git Rev News (see e.g. this discussion on git mailing list, but also ArsTechnica article and this this opinion)?

Edit: may need link to #git: an introduction

[tarsius]

I've released

• Magit 3.0.0 https://emacsair.me/2021/05/25/magit-3.0
• Forge 0.2.0 https://emacsair.me/2021/05/25/forge-0.2

Hooray 😀

[chriscool]

@jnareb yeah we could write about the Freenode issue. It's still recent though and https://git-scm.com/community still says that we are using Freenode. So it could also be a good idea for the next edition.

[chriscool]

@tarsius congrats about these releases! I wonder if we should add them to the "Releases" section or in the "Various" or "Git tools and sites" section. If you just want them added to the "Releases" section, I can do it. Otherwise we would need a few short sentences, maybe in a PR, announcing them.

[tarsius]

Just in the "Releases" section is fine.

[jnareb]

My links have landed in bdfe6cf

[chriscool]

Just in the "Releases" section is fine.

Ok, added in e97ae03

[chriscool]

Thanks @jnareb for the links!

[sivaraam]

In ac1aa68, I made 2 minor grammatical correction which I happened to notice when reading the draft. Kindly correct them if they look incorrect.

[mjaix]

Supplied my usual tiny fixes. @sivaraam: your ac1aa68 corrections are IMHO o.k., thanks a lot. In general, I prefer community based solutions with (100-n)%+ accuracy each definitely over a single hero trying to reach 100% :-).

[chriscool]

Thanks @sivaraam and @mjaix for the fixes!

[jnareb]

Should we write about issue with Freenode (where #git IRC channel is) in Git Rev News (see e.g. this discussion on git mailing list, but also ArsTechnica article and this this opinion)?

Edit: may need link to #git: an introduction

There is also an LWN.net article Turmoil at the freenode IRC network (free to access subscriber link)

[sivaraam]

I made one other small correction which I noted in 2ae3c72. Kindly revert it if it looks incorrect.

[chriscool]

Published and announced in https://lore.kernel.org/git/CAP8UFD0R9tm6ovC3VfAJLJo0nL9UXP7Zv6+O7d3AFDiQxOYSMg@mail.gmail.com/

[chriscool]

I made one other small correction which I noted in 2ae3c72. Kindly revert it if it looks incorrect.

Thanks @sivaraam ! It LGTM!