-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any comment about upcoming Git Rev News edition 115 #726
Comments
Some things we can talk about:
|
@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 |
@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 (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 |
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.
If talking about portability it might make more sense to link to
https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html#tag_19_09_02
instead, as 'pipefail' has recently been added to POSIX (issue 8).
(The TLDP link seems to be about Bash.)
|
@stepnem yeah, nice link, thanks! |
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 |
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
Thanks, I've fixed up the resulting merge conflict and
re-pushed my PR branch.
|
Sorry, Access from $work I difficult. |
Sorry, Access from $work I difficult, but now established .. |
The first link for "Host your own Radicle seed node" is actually linking to the previous bullet-point's GitVersion article. |
Published and announce email sent: https://lore.kernel.org/git/CAP8UFD1pRLHAxVQGQ-oxzKTDSp+EuspR8BtGhWNch8MRbcfBzw@mail.gmail.com/ Draft email was: https://lore.kernel.org/git/CAP8UFD350-iO7o0xAw9qg5f5uX8tN86so2TYf6AvD5Y1C=WyEA@mail.gmail.com/ |
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
The text was updated successfully, but these errors were encountered: