unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: chad <yandros@gmail.com>, "Óscar Fuentes" <ofv@wanadoo.es>,
	emacs-devel@gnu.org
Subject: Re: igc: trying to chase a crash
Date: Wed, 27 Nov 2024 03:52:09 -0500	[thread overview]
Message-ID: <yp1ttbtjbye.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m2a5dl5cvz.fsf@gmail.com> ("Gerd Möllmann"'s message of "Wed, 27 Nov 2024 08:55:44 +0100")

Gerd Möllmann <gerd.moellmann@gmail.com> writes:

> Andrea Corallo <acorallo@gnu.org> writes:
>
>>> I get the same feeling. Something is a bit odd.
>>
>> I don't find this too odd, I have my own ideas about the reasons for
>> this difference.
>
> Care to share your thoughts?

Sure if it's of interest: my idea of few things that helped a lot native
comp in gaining traction at time:

- publishing simple blog posts summarizing and explaining the progresses
  of the branch [1]

- native-comp being a feature branch, this clarified that the goal was
  merging to master (IOW something which was probably likely to happen)
  and that the branch was trackable by users.  That's why I suggested
  more than once this solution in the past.

- publishing some positive performance numbers in order to explain/prove
  the soundness of the approach.

That said, users were very interested and gave a lot of good feedbacks
and bug reports (my impression more than for igc), but the number of
developers involved I'm pretty sure was not higher than what igc got
already.

>>
>>> But maybe that's even a good thing,
>>
>> I respectfully disagree.
>>
>>   Andrea
>
> Just trying to always look at the bright side of life :-).

:)

[1] <https://akrl.sdf.org/gccemacs.html>



  reply	other threads:[~2024-11-27  8:52 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25 18:48 igc: trying to chase a crash Óscar Fuentes
2024-11-25 19:23 ` Eli Zaretskii
2024-11-25 19:53   ` Óscar Fuentes
2024-11-25 20:01     ` Eli Zaretskii
2024-11-25 20:51       ` Óscar Fuentes
2024-11-26  3:33         ` Eli Zaretskii
2024-11-26  5:17         ` Gerd Möllmann
2024-11-26 18:29           ` chad
2024-11-26 21:39             ` Andrea Corallo
2024-11-27  5:28               ` Gerd Möllmann
2024-11-27  7:50                 ` Andrea Corallo
2024-11-27  7:55                   ` Gerd Möllmann
2024-11-27  8:52                     ` Andrea Corallo [this message]
2024-11-27  9:12                       ` Gregor Zattler
2024-11-27  9:26                         ` Andrea Corallo
2024-11-27 10:02                           ` Gerd Möllmann
2024-11-27 10:25                             ` icg build instructions [was: Re: igc: trying to chase a crash] Andrea Corallo
2024-11-27 11:12                               ` Gerd Möllmann
2024-11-27 11:51                                 ` Óscar Fuentes
2024-11-27 14:23                                   ` Gerd Möllmann
2024-11-27 13:43                                 ` Andrea Corallo
2024-11-27 13:49                                   ` Andrea Corallo
2024-11-27 14:16                                   ` Gerd Möllmann
2024-11-28 12:46                                   ` Óscar Fuentes
2024-11-28 12:55                                     ` Gerd Möllmann
2024-11-28 13:00                                     ` Pip Cet via Emacs development discussions.
2024-11-28 14:10                                       ` Óscar Fuentes
2024-11-27 15:10                               ` Eli Zaretskii
2024-11-28  4:42                                 ` Gerd Möllmann
2024-11-28  9:35                                   ` Eli Zaretskii
2024-11-27 10:40                           ` igc: trying to chase a crash Vincenzo Pupillo
2024-11-27 10:44                             ` Andrea Corallo
2024-11-27 10:59                               ` Óscar Fuentes
2024-11-27 15:02                                 ` Andrea Corallo
2024-11-27 11:16                               ` Gerd Möllmann
2024-11-27 13:47                                 ` Andrea Corallo
2024-11-27 14:48                                   ` Gerd Möllmann
2024-11-27 15:04                                     ` Óscar Fuentes
2024-11-27 12:37                               ` Jeff Walsh
2024-11-27 15:11                             ` Eli Zaretskii
2024-11-27  9:55                       ` Gerd Möllmann
2024-11-27 10:01                         ` Andrea Corallo
2024-11-27 10:08                           ` Gerd Möllmann
2024-11-27 10:18                             ` scratch/igc as a feature branch [was: Re: igc: trying to chase a crash] Andrea Corallo
2024-11-27 15:08                               ` Eli Zaretskii
2024-11-28 10:56                                 ` Andrea Corallo
2024-11-28 11:59                                   ` Eli Zaretskii
2024-11-28 12:54                                     ` Gerd Möllmann
2024-11-28 12:57                                       ` Pip Cet via Emacs development discussions.
2024-11-28 13:12                                         ` Gerd Möllmann
2024-11-28 15:43                                       ` Andrea Corallo
2024-11-27 15:06                         ` igc: trying to chase a crash Eli Zaretskii
2024-11-28  4:46                           ` Gerd Möllmann

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=yp1ttbtjbye.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --cc=ofv@wanadoo.es \
    --cc=yandros@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 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).