Draft of Git Rev News edition 60

> Hi everyone!
> 
> A draft of a new Git Rev News edition is available here:
> 
>   https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-60.md
> 
> Everyone is welcome to contribute in any section either by editing the
> above page on GitHub and sending a pull request, or by commenting on
> this GitHub issue:
> 
>   https://github.com/git/git.github.io/issues/410
> 
> You can also reply to this email.
> 
> In general all kinds of contribution, for example proofreading,
> suggestions for articles or links, help on the issues in GitHub, and
> so on, are very much appreciated.
> 
> I tried to cc everyone who appears in this edition, but maybe I missed
> some people, sorry about that.
> 
> Jakub, Markus, Kaartic and me plan to publish this edition on Wednesday
> February 19th in the afternoon.
> 
> Thanks,
> Christian.

> I spotted a typo:
>
> "Many attempts at importers silently botch this in practice, but least it handled automatically in theory"
>
> should be
>
> "Many attempts at importers silently botch this in practice, but it can be handled automatically in theory"

> Hi Eric,
> 
> I have observed that you have used the expression *<word>* four times
> (see grep excerpt below) in your article - do you intend to have it
> printed like *different* 
> or just have it transformed to italic by Markdown?
> 
> Best regards,
> Markus

> Hi everyone!
> 
> A draft of a new Git Rev News edition is available here:
> 
>   https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-60.md
> 
> Everyone is welcome to contribute in any section either by editing the
> above page on GitHub and sending a pull request, or by commenting on
> this GitHub issue:
> 
>   https://github.com/git/git.github.io/issues/410
> 
> You can also reply to this email.
> 
> In general all kinds of contribution, for example proofreading,
> suggestions for articles or links, help on the issues in GitHub, and
> so on, are very much appreciated.
> 
> I tried to cc everyone who appears in this edition, but maybe I missed
> some people, sorry about that.
> 
> Jakub, Markus, Kaartic and me plan to publish this edition on Wednesday
> February 19th in the afternoon.
> 
> Thanks,
> Christian.

> On 2020.02.17 16:50, Christian Couder wrote:
> > Hi everyone!
> >
> > A draft of a new Git Rev News edition is available here:
> >
> >   https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-60.md
> >
> > Everyone is welcome to contribute in any section either by editing the
> > above page on GitHub and sending a pull request, or by commenting on
> > this GitHub issue:
> >
> >   https://github.com/git/git.github.io/issues/410
> >
> > You can also reply to this email.
> >
> > In general all kinds of contribution, for example proofreading,
> > suggestions for articles or links, help on the issues in GitHub, and
> > so on, are very much appreciated.
> >
> > I tried to cc everyone who appears in this edition, but maybe I missed
> > some people, sorry about that.
> >
> > Jakub, Markus, Kaartic and me plan to publish this edition on Wednesday
> > February 19th in the afternoon.
> >
> > Thanks,
> > Christian.
>
> A couple of typos and an IMO awkward phrasing, all in the "Git tools and
> sites" section:
>
> * In the "Github and Government" entry: s/Ggather/gather/
> * In the "Shell Git" entry: s/that a practical/than a practical/
> * In the "git-tfs" entry: s/no more actively/not actively/