Any comment about upcoming Git Rev News edition 58

[chriscool]

A currently mostly empty draft is there:

https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-58.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 December 18th 2019!

Thanks!

cc @jnareb @mjaix @sivaraam @gitster

[chriscool]

Left over issues suggested by @jnareb for previous edition:

• Should we auto-close PRs on git/git? - with a sidenote about "drive by" contributions
• [PATCH] bugreport: add tool to generate debugging info
• git branch --edit-description a custom file - or, ideas on how to version control and share branch descriptions and other metadata
• [RFC] xl command for visualizing recent history - depending on how it goes, it might be good example for a "Review" section, how idea and patch is incrementally improved (though possibly for the next edition)
• [PATCH 00/11] Improve the readability of log --graph output

[chriscool]

As I am very busy, let's publish this edition on Wednesday December 25th 2019, so for Christmas!

[nasamuffin]

Should the security updates be discussed? https://lore.kernel.org/git/xmqqr21cqcn9.fsf@gitster-ct.c.googlers.com/T/#u

[chriscool]

@nasamuffin yeah it would be a good idea to discuss it.

[prati0100]

A minor typo I noticed.

Miriam Rubio from Barcelona, Spain will be mentored by Christian Couder to work on the Finish converting git bisect from shell to C project.

Missing quotes around Miriam's project. So, it should instead be:

Miriam Rubio from Barcelona, Spain will be mentored by Christian Couder to work on the "Finish converting git bisect from shell to C" project.

[chriscool]

@prati0100 thanks for the suggestion. It should be fixed now!

[chriscool]

@nasamuffin the security releases are now mentioned in fbfc936
Thanks!

[phillipwood]

@chriscool I think my comment "having them as a feature of the rev listing machinery rather than specific to a particular command". about the ephemeral refs is really agreeing with @dscho rather than a new suggestion. As you say I was mostly in agreement with his ideas. I agreed that tying the ephemeral refs to the terminal was a good idea but though it should use getsid() rather than getppid() and I wasn't sure that they needed to be per worktree as well. Thanks.

[chriscool]

@phillipwood yeah, but I think it was interesting that you mentioned the rev list machinery first. Do you have an idea about how to improve on what I wrote?

[mjaix]

Hi, I applied my usual typo fixes (found only one this time). @phillipwood I tried to rephrase the article according to your suggestions. Hope that is ok, otherwise please place a suggestion/correction.

[sivaraam]

For the note, I made a slight change to the formatting of the Outreachy project titles in b010bdd as I felt that monospace was better suited for styling code.

[chriscool]

Published: https://public-inbox.org/git/CAP8UFD3wVjAU7pn=jrWO_ApfjxDuY6R5S62Q5-f1ygN+-ESM8g@mail.gmail.com/

@jnareb I couldn't wait for some links from you, so I added a few I found here and there.