From: Markus Jansen <mja@jansen-preisler.de>
To: esr@thyrsus.com, Christian Couder <christian.couder@gmail.com>
Cc: mja@jansen-preisler.de, 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>,
Emily Shaffer <emilyshaffer@google.com>,
Torsten Krah <krah.tm@gmail.com>,
Dennis Kaarsemaker <dennis@kaarsemaker.net>
Subject: Re: Draft of Git Rev News edition 60
Date: Wed, 19 Feb 2020 02:15:20 +0100 [thread overview]
Message-ID: <59c983e8b706838df77516e55c1f5f33bdb1a80d.camel@jansen-preisler.de> (raw)
In-Reply-To: <20200217160311.GA79320@thyrsus.com>
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
next prev parent reply other threads:[~2020-02-19 1:21 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 [this message]
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:
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=59c983e8b706838df77516e55c1f5f33bdb1a80d.camel@jansen-preisler.de \
--to=mja@jansen-preisler.de \
--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=jnareb@gmail.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=krah.tm@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).