Any comment about upcoming Git Rev News edition 69

[chriscool]

A currently mostly empty draft is there:

https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-69.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 November 25th 2020!

Thanks!

cc @jnareb @mjaix @sivaraam @gitster

[sivaraam]

@chriscool When do we plan to publish this edition? November 18th or November 25th? 🤔

[chriscool]

@sivaraam I meant November 25th as written in https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-69.md but I had forgotten to update the comment when I copy pasted it from the previous issue. It's fixed now. Thanks!

[jnareb]

I think it might be good idea to add a short note about planned deprecation and later removal of old .git/branches/ and .git/remotes/ way of specifying remote repositories.

See https://public-inbox.org/git/cover.1494509599.git.johannes.schindelin@gmx.de/t/#u

[chriscool]

@jnareb yeah, let's do that!

[PhilipOakley]

"Git is too Hard"

An interesting blog/podcast about the Git CLI, for those who work inside the terminal https://changelog.com/posts/git-is-simply-too-hard

This was in the CodeProject's daily news so may have some visibility.

[chriscool]

@PhilipOakley thanks! It was also on Hacker News.

[jnareb]

I have added my links in 66b6960 - it includes links to "Git is too Hard" blog/podcast mentioned by @PhilipOakley .

[chriscool]

Sorry I am very late. The script to automatically get the release information from many places broke for GitLab as they changed the format of their "releases" page and it is not so easy to fix.

[mjaix]

Hi, I tried to understand why https://git.github.io/rev_news/2020/08/27/edition-66/, https://git.github.io/rev_news/2020/10/30/edition-68/,  and the actual Rev News have a formatting which results in a very slim left menu colomn. Failed :-( ... hints are appreciated.  @chriscool: do you still plan to publish edition 69 tomorrow? cc @jnareb @sivaraam

[mjaix]

I had similar experiences when trying to enrich/augment IBM web pages with Ericsson/IBM internal information some years ago for an intranet page ...  after having had a look at the present GitLab release page, I got some idea of your trouble. Did you succeed in the end?

[mjaix]

Supplied some tiny fixes in 33601bf.

[chriscool]

@mjaix yeah, I don't understand either why https://git.github.io/rev_news/2020/08/27/edition-66/ and https://git.github.io/rev_news/2020/10/30/edition-68/ have a formatting which results in a very slim left menu column while https://git.github.io/rev_news/2020/09/24/edition-67/ looks ok.

Now I hope to publish edition 69 on Friday and to send a draft today.

[jnareb]

@chriscool , @mjaix : If I understand it correctly, 66 and 68 edition has a very slim left menu column because the contents column is exceedingly wide due to overly long line in the code block. The menu column starts in the same place, it is just that it has less place because content column crowds it.

I wonder if it would be possible in CSS to make the left margin slimmer instead of the menu column when contents column gets wide.

[chriscool]

Draft sent: https://lore.kernel.org/git/CAP8UFD10RsOi8_gdg-ZbcrN2HHaPyia096svnjmCu_U70LU_8g@mail.gmail.com/

Publication date changed to Friday Nov 27th.

[chriscool]

Thanks @sivaraam for the interview, @jnareb for the links and @mjaix for the fixes!

@jnareb thanks for finding the issue with the very slim left menu column. I think we should split overly long lines code blocks to avoid that, but I am also ok with making the left margin slimmer in CSS.