all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andrea Corallo via "Emacs development discussions." <emacs-devel@gnu.org>
To: Ethan Edwards <ethancarteredwards@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Speeding up native-comp progress
Date: Sun, 16 Aug 2020 14:06:39 +0000	[thread overview]
Message-ID: <xjfd03qadn4.fsf@sdf.org> (raw)
In-Reply-To: <20200816085043.vwju75c2ad2j2z7e@archlaptop.localdomain> (Ethan Edwards's message of "Sun, 16 Aug 2020 04:50:43 -0400")

Ethan Edwards <ethancarteredwards@gmail.com> writes:

> Hey all,
>
> I've started compiling my own emacs with my own ./configure flags,
> instead of my GNU/Linux Distro's binary. I also have took notice
> of the feature/native-comp git branch and compiled it and I've
> been using it for about a week and have loved it.
>
> On Reddit there's a post linking to the talk, and one of the comments on
> said post is saying that it would likely be Emacs 28 before it was
> merged, which is about 2 years away. I would like to know if there's
> anything I could do to help speed up that process, for example Bug
> Reports, or development, etc.

Hi Ethan,

thanks for the mail, is great to ear you enjoy using the branch.

On my side I think precise bug reports are _extremely_ important.  For
precise I especially mean providing a clear recipe to reproduce it
starting from scratch.  Precise bug reports saves me a lot of time and
greatly help improving the usability of the branch for all users.

Needless to say suggestions and/or patches are greatly appretiated too.

Thanks

  Andrea

--
akrl@sdf.org



  reply	other threads:[~2020-08-16 14:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-16  8:50 Speeding up native-comp progress Ethan Edwards
2020-08-16 14:06 ` Andrea Corallo via Emacs development discussions. [this message]
2020-08-16 14:49   ` Ethan Edwards
2020-08-16 15:32     ` Andrea Corallo via Emacs development discussions.

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=xjfd03qadn4.fsf@sdf.org \
    --to=emacs-devel@gnu.org \
    --cc=akrl@sdf.org \
    --cc=ethancarteredwards@gmail.com \
    /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.