From: Yuan Fu <casouri@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 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 12:14:58 -0400 [thread overview]
Message-ID: <83FC475A-5D09-4ED1-A0B3-BF85FEEAAC00@gmail.com> (raw)
In-Reply-To: <9d82c77d-a42f-42c0-8968-e8e572526999@default>
> On Apr 29, 2020, at 10:51 AM, Drew Adams <drew.adams@oracle.com> wrote:
>
>> 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?
>
I mentioned GitHub and its issue and pull request feature. I figure that’s what most people are familiar with nowadays.
Yuan
next prev parent reply other threads:[~2020-04-29 16:14 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
2020-04-29 16:14 ` Yuan Fu [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83FC475A-5D09-4ED1-A0B3-BF85FEEAAC00@gmail.com \
--to=casouri@gmail.com \
--cc=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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.