Any comment about upcoming Git Rev News edition 77

[chriscool]

A currently mostly empty draft is there:

https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-77.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 July 28th 2021!

Thanks!

cc @jnareb @mjaix @sivaraam @gitster

[sivaraam]

Hi all, Just wanted to note here that I couldn't get a candidate who could be interviewed for this edition. So, it looks like we've got to publish this one without the "Developer Spotlight".

[chriscool]

@sivaraam no worries and thanks for the update!

[jnareb]

My links have landed in 1b12169 , 0c8de12 and 21d223f .

[chriscool]

@jnareb great, thanks! By the way sorry I am late again but hopefully I will be able to send the draft today and we can publish on Friday July 30th...

[chriscool]

...actually it will be Saturday July 31st.

[chriscool]

Draft sent: https://lore.kernel.org/git/CAP8UFD38P_PYf3NzB2ULHbOTFNUCDXuZzasKKV5Cqgg7PrgQdg@mail.gmail.com/

[jnareb]

@chriscool - thank you for all your work.

Sidenote: at one time we switched from "tight" itemized list to "loose" itemized list for links to various articles. Is this something worth correcting?

• tight
• tight
• tight

vs

• loose

• loose

• loose

[chriscool]

@jnareb, I would say it's worth correcting, but as you are contributing the most to the links, I will let you decide on this. Thanks for noticing!

[newren]

I've got another post about merge-ort/diffcore-rename optimizations (reviewed by Christian nearly two months ago) up at
https://palantir.medium.com/optimizing-gits-merge-machinery-part-iv-5bbc4703d050. Part V (also reviewed by Christian) is also in the works and is supposed to be posted imminently, though I'm not sure if it'll show up before this edition is published.

[sivaraam]

I've got another post about merge-ort/diffcore-rename optimizations (reviewed by Christian nearly two months ago) up at
palantir.medium.com/optimizing-gits-merge-machinery-part-iv-5bbc4703d050.

@newren Added a link to your part IV in 8bd9b9e.

[chriscool]

Thanks @newren and @sivaraam!

[jnareb]

I have tightened the formatting of list of links, removing empty lines between items. The preview seems to suggest that it would result in a tighter list, taking less vertical space; items re short, so we don't need extra vertical space to separate them.

[mjaix]

I have supplied my really tiny set of corrections in dda1441 . Two items aroused personal feelings: First, I have been working on Sun workstations and servers for 20+ years. When I once found a C++ compiler errror, it took me less than 15 seconds to switch the patch level to use  in my ClearCase installation, but the Sun support engineer needed about almost a day due to SCCS in the backend and their time consuming patch mechanism in the front ... Second, I have come across the return vs. exit problem in the past in another context - that is, refactoring. Consider the case when you *ever* would like to call cmd_*() not as a "singleton command" from run_builtin() and/or with the aim to "try another route" in case the first cmd_*() call failed. From a server-side perspective, exit() is simply a no-go. Ruminations left unpublished. Cheers, Markus

[chriscool]

@jnareb thanks! It seems to me though that on https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-77.md the list under "Git tools and sites" is taking more vertical space than the other lists. I wonder if we should remove the blank lines between the list items.

@mjaix thanks for the corrections! Thanks also for your interesting comments about the article. It reminds me that both you and @sivaraam haven't appeared yet in the "Developer Spotlight" section...

[jnareb]

I think that if items on the list are larger, taking up more than a line or a few lines, it is better to have larger vertical separation between items on the list. But feel free to remove empty lines between items in the Markdown source to make the list tighter; this is just my opinion.

[chriscool]

@jnareb ok, I will not change that.

[chriscool]

Published and announced in: https://lore.kernel.org/git/CAP8UFD0V-ZVvt=8UYJ+AiAoQET449LRJAa+wgf92pkRwWs86aA@mail.gmail.com/