From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 74805@debbugs.gnu.org, stefankangas@gmail.com, kbrown@cornell.edu
Subject: bug#74805: 30.0.92; Trying to build scratch/igc on Cygwin
Date: Thu, 12 Dec 2024 16:01:03 +0100 [thread overview]
Message-ID: <m21pydosi8.fsf@gmail.com> (raw)
In-Reply-To: <86ldwlynjk.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 12 Dec 2024 16:38:07 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> I haven't done anything like that. I've only submitted some minor Github
>> issue when I was playing with MPS, and I've sent them a mail to let them
>> know what's going on when I made what I had public here on emacs-devel.
>
> So maybe we should ask them. It could be a factor in our decision
> whether we want to fork MPS and maintain our own fork.
Yes, I think something "official" from the maintainers would be a good
thing. The email I used back then to inform them of what's
going on was info@ravenbrook.com. Couldn't find something better.
prev parent reply other threads:[~2024-12-12 15:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 22:50 bug#74805: 30.0.92; Trying to build scratch/igc on Cygwin Ken Brown
2024-12-11 23:47 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-12 18:14 ` Ken Brown
2024-12-11 23:57 ` Andrea Corallo
2024-12-12 6:09 ` Eli Zaretskii
2024-12-12 18:12 ` Ken Brown
2024-12-12 19:25 ` Eli Zaretskii
2024-12-12 23:17 ` Stefan Kangas
2024-12-13 7:51 ` Eli Zaretskii
2024-12-20 23:48 ` Ken Brown
2024-12-21 7:24 ` Eli Zaretskii
2024-12-21 16:56 ` Ken Brown
2024-12-21 17:21 ` Gerd Möllmann
2024-12-21 17:34 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-21 20:25 ` Ken Brown
2024-12-22 8:24 ` Richard Brooksby
2024-12-22 8:32 ` Richard Brooksby
2024-12-12 11:05 ` Stefan Kangas
2024-12-12 11:30 ` Eli Zaretskii
2024-12-12 12:06 ` Gerd Möllmann
2024-12-12 14:38 ` Eli Zaretskii
2024-12-12 15:01 ` Gerd Möllmann [this message]
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=m21pydosi8.fsf@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=74805@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=kbrown@cornell.edu \
--cc=stefankangas@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.