unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Jean-Christophe Helary
	<jean.christophe.helary@traduction-libre.org>,
	Emacs developers <emacs-devel@gnu.org>
Subject: RE: Review a blog post about emacs-devel
Date: Wed, 29 Apr 2020 07:51:32 -0700 (PDT)	[thread overview]
Message-ID: <9d82c77d-a42f-42c0-8968-e8e572526999@default> (raw)
In-Reply-To: <12E8521E-FDD7-4AE9-B578-7F23D3D64F25@traduction-libre.org>

> Can I suggest that you replace '"modern" open source workflows' with "recent ..."

+1.

But better yet, say what you really mean by 
that.  What particular features/qualities
define/describe that class?  No need to be
exhaustive, but some mention of _something_
would help.

There's nothing _inherently_ important or
interesting about a workflow being recent
or "modern".  What about those workflows
you have in mind is relevant here?



  parent reply	other threads:[~2020-04-29 14:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-27 20:58 Review a blog post about emacs-devel Yuan Fu
2020-04-27 21:31 ` Noam Postavsky
2020-04-27 21:37   ` Yuan Fu
2020-04-29  6:33 ` Colin Baxter
2020-04-29  6:49 ` Jean-Christophe Helary
2020-04-29 14:08   ` Yuan Fu
2020-04-29 14:51   ` Drew Adams [this message]
2020-04-29 16:14     ` Yuan Fu
2020-04-30  2:28 ` Richard Stallman
2020-04-30 15:19   ` Yuan Fu
2020-04-30 16:42     ` Dmitry Gutov
2020-04-30 15:52   ` Stefan Kangas
2020-04-30 16:26   ` 조성빈
2020-04-30 16:50     ` Stefan Kangas
2020-05-02 18:58       ` Yuan Fu
2020-05-05  7:56         ` Jean-Christophe Helary
2020-05-07 19:40           ` Yuan Fu
2020-05-15  2:57             ` Yuan Fu
2020-05-15  5:55               ` Clément Pit-Claudel
2020-05-15 16:22                 ` Yuan Fu
2020-05-15  6:52               ` Eli Zaretskii
2020-05-15 16:20                 ` Yuan Fu

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: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=9d82c77d-a42f-42c0-8968-e8e572526999@default \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=jean.christophe.helary@traduction-libre.org \
    /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://git.savannah.gnu.org/cgit/emacs.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).