From: Noam Postavsky <npostavs@gmail.com>
To: Yuan Fu <casouri@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Review a blog post about emacs-devel
Date: Mon, 27 Apr 2020 17:31:37 -0400 [thread overview]
Message-ID: <CAM-tV--BNAb6OcpPnJZQ8Qyq1JwO7zBhcyeBLGCTfZf-u1WLEg@mail.gmail.com> (raw)
In-Reply-To: <2D56B465-C028-41AE-8D07-38C1C49FF5F7@gmail.com>
On Mon, 27 Apr 2020 at 16:58, Yuan Fu <casouri@gmail.com> wrote:
>
> I wrote a blog post about how to participate in emacs-devel in the hope that this will help with people who wants to contribute. Before I publish it, could some one have a look at it to see if there is misinformation? Any advice/concern is welcome. Thanks.
> On the other hand, don’t send a bug report without a patch to
> emacs-devel, report it as a bug (even if you are not sure if it should
> be classified as a bug, report it as a bug).
You can (and generally should) send bug reports/feature requests even
with patches to the bug list.
next prev parent reply other threads:[~2020-04-27 21:31 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 [this message]
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
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=CAM-tV--BNAb6OcpPnJZQ8Qyq1JwO7zBhcyeBLGCTfZf-u1WLEg@mail.gmail.com \
--to=npostavs@gmail.com \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.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).