Closed chriscool closed 5 years ago
Topics that might be interesting to add to this edition (not all of them, probably):
core.featureAdoptionRate
and changed scope -- about meta-configuration that changes default values for some specific config settings.mailmap
by default in more places)Also, new links:
@jnareb I think the links to the GSoC blogs have been given in https://git.github.io/rev_news/2019/05/22/edition-51/ already.
I am not so sure the results of the intermediary GSoC evaluations are very interesting. Anyway both students passed these evaluations.
Thanks for the other ideas though!
As a side note: the translations of the manpages are available on git-scm.com. For instance: https://git-scm.com/docs/git-add/pt_BR
Just contributed my usual tiny typo and structure fixes.
Best regards, Markus
Added a few links in "Light reading" section in ce9c307
Topics that might be interesting to add to this edition (not all of them, probably):
- [ ] ~results of intermediary GSoC evaluation~
True, the results of the intermediary GSoC evaluations might not be interesting enough
- [ ] [PATCH 00/11] [RFC] Create 'core.size=large' setting to update config defaults, later renamed to
core.featureAdoptionRate
and changed scope -- about meta-configuration that changes default values for some specific config settings
The discussion continues, so it perhaps be better postponed for the next edition.
- [x] [PATCH 0/6] easy bulk commit creation in tests, resulting from detailed analysis of Git Test Coverage Report (Thurs. June 27)
Thanks @chriscool for the writeup.
- [ ] specifying revision - how to enforce matching a tag/branch-name or revision only, resulting in proposed patch to add new extended SHA-1 syntax to control resolution process
- [ ] Deadname rewriting -- how to handle legal name change (answer: use
.mailmap
by default in more places)
@mjaix and @jnareb thanks for your improvements and additions!
@jnavila thanks for the information, but I don't know much about the translations of the manpages. Could you explain a little bit more, for example what happened, who contributed what, and how it's possible to see what's available? If you don't have time now, this could go in the next edition. By the way are you ok to be interviewed in the next edition?
@jnareb about the topics you suggest that haven't been covered in this edition, I think that as usual I will copy them to the issue for the next edition. Thanks anyway for them! I find it very useful and time saving to get good suggestions like this!
@chriscool for the moment, the project of translation of the manpages leaves outside the Git project. There were some patches in the main repo to allow to reuse the Makefiles rules for translated content. The timing for writing a blurb on this for tomorrow is too short indeed. Please ping me when you need some content for the next Git Rev News issue. By that time, I hope to have more to say.
A currently mostly empty draft is there:
https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-53.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 24th 2019!
Thanks!
cc @jnareb @mjaix @gaalcaras @gitster