Draft of Git Rev News edition 60

Draft of Git Rev News edition 60

[Christian Couder]

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.

Re: Draft of Git Rev News edition 60

[Eric S. Raymond]

Christian Couder <christian.couder@gmail.com>:
> 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"
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

Re: Draft of Git Rev News edition 60

[Christian Couder]

On Mon, Feb 17, 2020 at 5:03 PM Eric S. Raymond <esr@thyrsus.com> wrote:

> 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"

Fixed!

Thanks,
Christian.

Re: Draft of Git Rev News edition 60

[Markus Jansen]

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


~/git/git.github.io> egrep '\*[a-z]+\*' rev_news/drafts/edition-60.md 
it as a DSL (domain-specific language) designed to be *scripted* --
to actually *need* the full power of a domain-specific language
*different* version-control systems, you have to deal with the
problem so deep that the *very* complete

Re: Draft of Git Rev News edition 60

[Eric S. Raymond]

Markus Jansen <mja@jansen-preisler.de>:
> 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

Italic or bold,. whatever fits your house style best.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

Re: Draft of Git Rev News edition 60

[Josh Steadmon]

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/

Re: Draft of Git Rev News edition 60

[Jakub Narębski]

On Wed, 19 Feb 2020 at 01:00, Josh Steadmon <steadmon@google.com> wrote:
> 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/

Thanks, should be fixed now.

-- 
Jakub Narębski