git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Markus Jansen <mja@jansen-preisler.de>
Cc: git <git@vger.kernel.org>, "Junio C Hamano" <gitster@pobox.com>,
	"Jakub Narebski" <jnareb@gmail.com>,
	"Kaartic Sivaraam" <kaartic.sivaraam@gmail.com>,
	"Jeff King" <peff@peff.net>,
	"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
	"Elijah Newren" <newren@gmail.com>,
	"Taylor Blau" <me@ttaylorr.com>,
	"Martin Ågren" <martin.agren@gmail.com>,
	"German Lashevich" <german.lashevich@gmail.com>
Subject: Re: Draft of Git Rev News edition 78
Date: Tue, 31 Aug 2021 15:36:43 +0200	[thread overview]
Message-ID: <CAP8UFD21pDJtgEF4_btkMmasQhFmjZst26uXHubzDO=gNMuPAw@mail.gmail.com> (raw)
In-Reply-To: <b4636123648204338ee2c6180a1822b2a9a65c4c.camel@jansen-preisler.de>

On Sun, Aug 29, 2021 at 11:36 PM Markus Jansen <mja@jansen-preisler.de> wrote:
>
> Tried to sort out tenses in the story, and added my usual tiny amount of correction suggestions in 34d65d4.
> As usual, feel free to further correct/revert/rephrase etc.

Thanks for the fixes! They LGTM!

> I like the backreferences to past editions, which I regard being a build-up mechanism for a collective/community memory :-).

Yeah, it's a balance between making things more useful without making
the text harder to read. But I think so far the result has been
positive.

      parent reply	other threads:[~2021-08-31 13:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-29 10:21 Draft of Git Rev News edition 78 Christian Couder
2021-08-29 10:23 ` Christian Couder
2021-08-29 19:53   ` Philip Oakley
2021-08-31 13:30     ` Christian Couder
     [not found]   ` <b4636123648204338ee2c6180a1822b2a9a65c4c.camel@jansen-preisler.de>
2021-08-31 13:36     ` Christian Couder [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='CAP8UFD21pDJtgEF4_btkMmasQhFmjZst26uXHubzDO=gNMuPAw@mail.gmail.com' \
    --to=christian.couder@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=german.lashevich@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=martin.agren@gmail.com \
    --cc=me@ttaylorr.com \
    --cc=mja@jansen-preisler.de \
    --cc=newren@gmail.com \
    --cc=peff@peff.net \
    /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).