From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Andrea Corallo <acorallo@gnu.org>
Cc: chad <yandros@gmail.com>, "Óscar Fuentes" <ofv@wanadoo.es>,
emacs-devel@gnu.org, "Pip Cet" <pipcet@protonmail.com>
Subject: Re: igc: trying to chase a crash
Date: Wed, 27 Nov 2024 11:08:41 +0100 [thread overview]
Message-ID: <m2wmgp3s5y.fsf@gmail.com> (raw)
In-Reply-To: <yp1ldx5j8qn.fsf@fencepost.gnu.org> (Andrea Corallo's message of "Wed, 27 Nov 2024 05:01:36 -0500")
Andrea Corallo <acorallo@gnu.org> writes:
>> If that's a requirement, maybe it is the reason why users are ignoring
>> igc, indeed. And in that case, the question would be, if the project or
>> some individual(s) could or want to do something similar. Which I can't
>> answer. I won't do it, though, which I think I said already too often.
>> And, from my POV, no one can be blamed for not having that stamina.
>
> Absolutely, still I think few things are probably really low cost (the
> feature branch comes to my mind).
>
Maintainers could just decide to do it, cough, cough :-). But I don't
have a say in this, Pip added to CC.
next prev parent reply other threads:[~2024-11-27 10:08 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
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 [this message]
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=m2wmgp3s5y.fsf@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=acorallo@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
--cc=pipcet@protonmail.com \
--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).