-
Notifications
You must be signed in to change notification settings - Fork 279
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 112 #714
Comments
In the issue for the previous edition @jnareb suggested:
|
@davvid right, thanks! This should be fixed now. |
My links have been added in e8bc2b9 (including one LWN.net SubscriberLink). |
Hi all, At best, it seems like an unnecessarily long way to say the only real difference is the terminology that Github and Gitlab use. Towards the end they also mention "Beyond terminology, there might be slight variations in functionalities depending on the platform. GitLab offers features like:" and they list:
But this implies that Github doesn't offer these features when in fact they do. I don't think there's anything wrong with plugging a product at the end of a post but it didn't feel like they really tried to write a useful post. Thanks and I appreciate all the work you all do in putting together the newsletter! |
Hi Chris,
sorry that I did not have time yesterday - I plan to look over edition
112 before 13:00 today, if that's OK with you.
I am pretty sure @stepnem and other already caught most errors (if not
all :-).
Best regards,
Markus
…On Sat, 2024-06-01 at 13:33 -0700, Christian Couder wrote:
A currently mostly empty draft is there:
https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-112.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 June 2024!
Thanks!
cc @jnareb [1] @mjaix [2] @sivaraam [3] @gitster [4] @stepnem [5]
—
Reply to this email directly, view it on GitHub [6], or unsubscribe
[7].
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Dipl.-Ing. Markus Jansen Alte Vaalser Str. 40a
Mob. +49 172 2742003 52074 Aachen/Aix-la-chapelle/Aken/Oche
Tel. +49 241 5592439 Deutschland/Allemagne/Germany/Duitsland/Tyskland
Fax +49 241 5592441 ***@***.***
[1] @jnareb https://github.com/jnareb
[2] @mjaix https://github.com/mjaix
[3] @sivaraam https://github.com/sivaraam
[4] @gitster https://github.com/gitster
[5] @stepnem https://github.com/stepnem
[6] view it on GitHub #714
[7] unsubscribe
https://github.com/notifications/unsubscribe-auth/ABB5P23Q35EOGRPVT4YL2M3ZFIVYBAVCNFSM6AAAAABIUNV5QWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZDSMZSG42DANQ
|
Hi @mjaix, no worries. 13:00 CET is OK for me. |
@mjaix your changes look great, thanks! |
Published and announced in: https://lore.kernel.org/git/CAP8UFD3v2o=3wg+1g=4pt6bpeKWT3T7z1z8DX6hyuiBnEKQdPw@mail.gmail.com/ |
A currently mostly empty draft is there:
https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-112.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 June 2024!
Thanks!
cc @jnareb @mjaix @sivaraam @gitster @stepnem
The text was updated successfully, but these errors were encountered: