-
Notifications
You must be signed in to change notification settings - Fork 292
Any comment about upcoming Git Rev News edition 103 #660
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
Comments
Suggestion by @jnareb from previous edition issue: Fetching too many tags? - contains interesting info about how Git fetches from remote repository |
Would this issue include conclusion of Google Summer of Code (GSoC 2023) program for Git, or is it too early? |
Thanks for the nudge, @jnareb. I think we're good to write about this in this edition. If someone doesn't beat me to it, I'll look into opening a PR adding the GSoC conclusion :-) |
I've raised the PR #664 to add the conclusion of GSoC 2023. |
Draft email sent: https://lore.kernel.org/git/CAP8UFD1qDet8OPKYgk6dgibPT4PW=AeO7T3h=_vz5uYnEOzO3Q@mail.gmail.com/ I also emailed @ttaylorr to get a link to a read only version of the Git Contributor's Summit (which happened last Tuesday and Wednesday) notes. |
Thanks @jnareb for the suggestion! The article I wrote is about this. |
My links have landed in 3b524c7 (might add part 2, currently Internet too flaky for me to check few of saved links - or there are problems with access to those sites from my part of Internet). BTW, on Git Virtual Contributor's Summit 2023 there was talk about maybe relaxing handing of Git trademark... and those links include tools and services with "Git" in their name: Gitness, Gitopia, GitButler, Gitamic, git-ssb. |
I plan to supply the usual fixes in the early afternoon today (that is,
around 15:00). Sorry for the delay.
|
Thanks for the information, but 15:00 in what timezone? |
One more link landed in 615e79e, and two more in e1b5705 . I have not added links to social media (Mastodon ~= federated Twitter/X, Lemmy ~= federated Reddit).
I have also decided not to add “Good Commit” vs “Your Commit”: How to Write a Perfect Git Commit Message, because it is Medium member-only story. |
No worries. I will wait for them. In the meantime, @stepnem already suggested some fixes that I merged. |
@jnareb thanks for the great links! |
Supplied a tiny amount of tiny fixes with 13d2f8c - sorry for the
delay.
@jnareb: I usually mean (C)EST.
Due to some vacation starting tomorrow morning, I would like to publish
the email in the late evening
unless there a concerns.
|
@mjaix thanks for your fixes! Ok with sending the email version late this evening. I am going to publish and announce the web version now. |
Published and announce email sent: https://lore.kernel.org/git/CAP8UFD2gCExE9J5wHnqr0yW5sayZ9ckvXo3KO76oCA+Peas27Q@mail.gmail.com/ |
A currently mostly empty draft is there:
https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-103.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 September 27th 2023!
Thanks!
cc @jnareb @mjaix @sivaraam @gitster
The text was updated successfully, but these errors were encountered: