git/git.github.io

Any comment about upcoming Git Rev News edition 115

Closed this issue · 16 comments

chriscool commented

A currently mostly empty draft is there:

https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-115.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 around the end of September 2024!

Thanks!

cc @jnareb @mjaix @sivaraam @gitster @stepnem

chriscool commented

Some things we can talk about:

  • results of GSoC 2024
  • Git participating in the next Outreachy round
  • Git Merge 2024
jnareb commented

My links have landed in 78f48f9 (with little addition in f699ee9).

chriscool commented

@jnareb thanks for the great links!

About your little addition, I think it's a good idea to talk about it, but I left a comment: f699ee9#commitcomment-147419315

chriscool commented

@mjaix thanks for your great fixes in ef17404 and 7047716!

However, about "In summary, the root problem can be understood as a portability one." that you added, I am not sure it's very clear why it's only a portability issue, as I am not sure Git would use the pipefail option even if it was available everywhere. I think that Git shell scripts just use no (or perhaps very few) shell options for a number of reasons, not just portability ones.

(For example, one of the benefits of using very few options is that it's easier for readers to understand what a snippet of code or a patch hunk does without having to look around everywhere for which options might or might not be set in the context of the snippet or hunk.)

It might be a good idea to add links to "the pipefail option" and "named pipes", like perhaps this one https://tldp.org/LDP/abs/html/options.html#OPTIONSREF (for the pipefail option) let me know if you want me to do it.

stepnem commented
chriscool commented

@stepnem yeah, nice link, thanks!

stepnem commented
jnareb commented

I've submitted #731 with a few nits I've found, but I also don't understand what "xs-related tools" in the Stacked Diffs paragraph refer to. Searching for "xs" in the current draft or the mentioned edition 111 didn't help. Am I missing something?

Good find. It was a typo (Ctrl+X Ctrl+S is save file in GNU Emacs, and if Ctrl does not take...). Fixed in fd76e5b

stepnem commented
chriscool commented

Thanks @stepnem , your PR is merged!

I would have hoped to have a reply from @mjaix but I am going to publish the edition in a few hours anyway.

mjaix commented

Sorry, Access from $work I difficult.

mjaix commented

Sorry, Access from $work I difficult, but now established ..
Feel free to leave out my hallucination regarding portability, or even the complete part in brackets.

steadmon commented

The first link for "Host your own Radicle seed node" is actually linking to the previous bullet-point's GitVersion article.

chriscool commented

@mjaix I think portability is a part of the issue but not the only one. I will change the part in brackets a bit. Thanks for your reply!

@steadmon thanks for the report! I will try to change the link.

chriscool commented

@steadmon link changed in 57bdc63

@mjaix changes made in 3516914