mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Eric S. Raymond" <>
To: Christian Couder <>
Cc: git <>, Junio C Hamano <>,
	Jakub Narebski <>,
	Markus Jansen <>,
	Kaartic Sivaraam <>,
	Jeff King <>,
	Johannes Schindelin <>,
	Emily Shaffer <>,
	Torsten Krah <>,
	Dennis Kaarsemaker <>
Subject: Re: Draft of Git Rev News edition 60
Date: Mon, 17 Feb 2020 11:03:11 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Christian Couder <>:
> Hi everyone!
> A draft of a new Git Rev News edition is available here:
> 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:
> 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="">Eric S. Raymond</a>

  reply	other threads:[~2020-02-17 16:11 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 [this message]
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

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:

  List information:

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

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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

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).