git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Jakub Narębski" <jnareb@gmail.com>
To: Josh Steadmon <steadmon@google.com>,
	Christian Couder <christian.couder@gmail.com>,
	git <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>,
	Jakub Narebski <jnareb@gmail.com>,
	Markus Jansen <mja@jansen-preisler.de>,
	Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
	Jeff King <peff@peff.net>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Emily Shaffer <emilyshaffer@google.com>,
	Torsten Krah <krah.tm@gmail.com>,
	Dennis Kaarsemaker <dennis@kaarsemaker.net>,
	Eric Raymond <esr@thyrsus.com>
Subject: Re: Draft of Git Rev News edition 60
Date: Wed, 19 Feb 2020 01:45:22 +0100	[thread overview]
Message-ID: <CANQwDwc-Ain79cfetz2YKY5FxrtbWaQgND4xzvg2LsAGOUqQOg@mail.gmail.com> (raw)
In-Reply-To: <20200219000033.GA12115@google.com>

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

      reply	other threads:[~2020-02-19  0:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 15:50 Draft of Git Rev News edition 60 Christian Couder
2020-02-17 16:03 ` Eric S. Raymond
2020-02-17 18:07   ` Christian Couder
2020-02-19  1:15   ` Markus Jansen
2020-02-19  1:29     ` Eric S. Raymond
2020-02-19  0:00 ` Josh Steadmon
2020-02-19  0:45   ` Jakub Narębski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANQwDwc-Ain79cfetz2YKY5FxrtbWaQgND4xzvg2LsAGOUqQOg@mail.gmail.com \
    --to=jnareb@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=christian.couder@gmail.com \
    --cc=dennis@kaarsemaker.net \
    --cc=emilyshaffer@google.com \
    --cc=esr@thyrsus.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=krah.tm@gmail.com \
    --cc=mja@jansen-preisler.de \
    --cc=peff@peff.net \
    --cc=steadmon@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).