unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: akrl@sdf.org
Cc: emacs-devel@gnu.org
Subject: Re: Profiling native-compilation
Date: Fri, 23 Apr 2021 13:52:59 +0300	[thread overview]
Message-ID: <83fszhnugk.fsf@gnu.org> (raw)
In-Reply-To: <83h7jxnuno.fsf@gnu.org> (message from Eli Zaretskii on Fri, 23 Apr 2021 13:48:43 +0300)

> Date: Fri, 23 Apr 2021 13:48:43 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: emacs-devel@gnu.org
> 
> > From: Andrea Corallo <akrl@sdf.org>
> > Cc: Eli Zaretskii <eliz@gnu.org>
> > Date: Fri, 23 Apr 2021 08:57:55 +0000
> > 
> > BTW to get an idea, I know is not defined but very roughly how much time
> > do we have before the 28 release branch is cut?  To get a feeling of how
> > much and what we can hope to fit into.
> 
> Hard to say, but I think at least a year, including the pretest phase.

Sorry, I missed the part about cutting the release branch.  That would
be sooner, perhaps 8 months from now?  But it also depends on what
other features we will want to include.  For example, if we decide to
include the pgtk branch, it could take more (I have no clear idea how
ready that branch is for landing, and I have the impression that the
branch is not tested by enough people, nowhere near the native-comp
branch).



  reply	other threads:[~2021-04-23 10:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-23  7:10 Profiling native-compilation Eli Zaretskii
2021-04-23  8:45 ` Andrea Corallo via Emacs development discussions.
2021-04-23  8:57   ` Andrea Corallo via Emacs development discussions.
2021-04-23 10:48     ` Eli Zaretskii
2021-04-23 10:52       ` Eli Zaretskii [this message]
2021-04-23 10:47   ` Eli Zaretskii
2021-04-23 13:46     ` 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

  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=83fszhnugk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=akrl@sdf.org \
    --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).