search

git / git.github.io

Git Developer Pages (This is NOT the place to discuss Git issues. See: https://git-scm.com/community)
https://git.github.io
314 stars 281 forks source link

Any comment about upcoming Git Rev News edition 69 #463

Closed chriscool closed 3 years ago

chriscool commented 3 years ago

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 commented 3 years ago

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

chriscool commented 3 years ago

@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 commented 3 years ago

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 commented 3 years ago

@jnareb yeah, let's do that!

PhilipOakley commented 3 years ago

"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 commented 3 years ago

@PhilipOakley thanks! It was also on Hacker News.

jnareb commented 3 years ago

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

chriscool commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

Supplied some tiny fixes in 33601bf.

chriscool commented 3 years ago

@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 commented 3 years ago

@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.

GitRevNews-wide GitRevNews-narrow

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 commented 3 years ago

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

Publication date changed to Friday Nov 27th.

chriscool commented 3 years ago

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.

sivaraam commented 3 years ago

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.

That's my understanding too. I've observed this several times before and have been wanting to create an issue about this but never got around to it.

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.

Another way to fix this would be to ensure code blocks always take up a fixed width rather than taking up as much width as it wants. I'm thinking of something similar to how code blocks in GitHub issue comments wrap withing the comment box. If that could be achieved, we wouldn't have to worry about how long the code block is.

felipec commented 3 years ago

Shouldn't the report about git pull warning and the subsequent patch series trying to improve the situation be worthwhile to mention?

This BTW revives the old discussion, so it's interesting something that wasn't fixed in 2014 is still biting us today.

PhilipOakley commented 3 years ago

Another thought for potential inclusions (given the git pull comment) could the the new and changed config variables (documentation & code) that have graduated to next/main so that these new / changed features and defaults become known. Probably something that can be deferred to the next Git Rev News

sivaraam commented 3 years ago

I just noticed that both the "Light reading" and "Git tools and sites" have an entry with a short paragraph that talk about nbdev. I wonder if they're a bit redundant.

Should we only mention the article in "Light reading" and talk about nbdev in "Git tools and sites"? Or are they fine as it is? 🤔

mjaix commented 3 years ago

Added some more tiny fixes in f210744, whithout changing the contents.

Also stumbled across the double nbrev mention - maybe that info should be merged in one of the places.

chriscool commented 3 years ago

I agree that nbdev mentions should be merged in one place. @jnareb as you added the mentions, can you do that, or do you want me to do it?

chriscool commented 3 years ago

@felipec and @PhilipOakley thanks for the suggestions! I will add them to the issue for the next edition, as it's too late to add them in this edition anyway and the discussions may not be finished. I will see what I can do next month. Feel free to start an article or a short news about them in the meantime.

chriscool commented 3 years ago

Published and announced in https://lore.kernel.org/git/CAP8UFD0xoqVh=1BweBqNOt4_9xg4GvDd7Jf5f5_5z4H+PCVt8g@mail.gmail.com/.

felipec commented 3 years ago

This should be closed. No?

felipec commented 3 years ago

@jnareb 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.

Yes. It is conceptually different, but I explain how in the pull request #471.

It ends up looking like this.

chriscool commented 3 years ago

This should be closed. No?

I usually wait for a few weeks before closing, as sometimes people have remarks about an edition that was just published.