-
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 113 #721
Comments
We should probably mention Git Merge tickets being available: https://lore.kernel.org/git/[email protected]/ |
I recently came across the following article. Not sure how relevant it is. Kindly check and include it if it seems relevant, @jnareb |
My links have landed in dd9cd97 Though I am bit unsure about the last link in "Light reading" subsection.
Thanks for the suggestion, @sivaraam ! Interesting article (and provides nice contrast to the first article on the list). I have added the link to the above article in 5eb1315 |
Thanks, Jakub. That first article is a great read on the history of Git. It's written pretty well. Thanks for sharing! |
@jnareb you might want to add https://about.gitlab.com/blog/2024/07/29/whats-new-in-git-2-46-0/ to your links. FYI these days the Gitaly team at GitLab is trying to have a blog post ready to post when each new Git feature version is released. |
Yeah, thanks @jnareb for the great links especially this one. |
Thanks for the link. Added in 8f35e72. |
Edition published and announced in: https://lore.kernel.org/git/CAP8UFD1w05CX-Z20cGC=yhEzhMfWU6vOegymKBLVYNxnQANvVQ@mail.gmail.com/ |
A currently mostly empty draft is there:
https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-113.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 July 2024!
Thanks!
cc @jnareb @mjaix @sivaraam @gitster @stepnem
The text was updated successfully, but these errors were encountered: