unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Helmut Eller <eller.helmut@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: pipcet@protonmail.com,  gerd.moellmann@gmail.com,
	 emacs-devel@gnu.org, jcm@SDF.ORG
Subject: Re: Helping with MPS
Date: Wed, 21 Aug 2024 19:44:31 +0200	[thread overview]
Message-ID: <87seuxdb40.fsf@gmail.com> (raw)
In-Reply-To: <86zfp5ubya.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 21 Aug 2024 18:34:21 +0300")

On Wed, Aug 21 2024, Eli Zaretskii wrote:

>> > But if we fork, why not simply add it to the Emacs Git repository? why
>> > do we need a separate repository on GitHub?
>> 
>> Putting a fork on GitHub seems like the courteous thing to do IMO.
>
> Not sure I understand: courteous to whom?  If we are going to make
> Emacs-specific changes in the library, who else will find this fork
> useful except people that build and develop Emacs?

Maybe Ravenbrook would like to see what does and doesn't work with MPS.



  reply	other threads:[~2024-08-21 17:44 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-20 15:37 Helping with MPS Jonathon McKitrick via Emacs development discussions.
2024-08-20 15:52 ` Pip Cet
2024-08-20 20:41   ` Jonathon McKitrick via Emacs development discussions.
2024-08-20 20:44     ` Jonathon McKitrick via Emacs development discussions.
2024-08-21  6:31   ` Helmut Eller
2024-08-21  6:56     ` Gerd Möllmann
2024-08-21  8:02     ` Pip Cet
2024-08-21  9:23       ` Helmut Eller
2024-08-21 13:53     ` Eli Zaretskii
2024-08-21 14:36       ` Helmut Eller
2024-08-21 14:44         ` Eli Zaretskii
2024-08-21 15:10           ` Helmut Eller
2024-08-21 15:34             ` Eli Zaretskii
2024-08-21 17:44               ` Helmut Eller [this message]
2024-08-21 18:06                 ` Eli Zaretskii
2024-08-20 16:05 ` Helmut Eller
2024-08-20 21:42   ` Jonathon McKitrick via Emacs development discussions.
2024-08-21  3:46     ` Gerd Möllmann
2024-08-21  5:59       ` Helmut Eller
2024-08-21  6:28       ` Arash Esbati
2024-08-21  6:54         ` Gerd Möllmann
2024-08-21 14:10       ` Jonathon McKitrick via Emacs development discussions.
2024-08-21 14:48         ` Gerd Möllmann
2024-08-21 15:08           ` Jonathon McKitrick via Emacs development discussions.
2024-08-21 15:40             ` Gerd Möllmann
2024-08-21 15:46               ` Jonathon McKitrick via Emacs development discussions.
2024-08-21 16:23                 ` Gerd Möllmann
2024-08-21 18:00                   ` Jonathon McKitrick via Emacs development discussions.
2024-08-21 18:04                     ` Gerd Möllmann
2024-08-21 18:20                       ` Jonathon McKitrick via Emacs development discussions.
2024-08-21 18:43                         ` Gerd Möllmann
2024-08-21 20:42                           ` Jonathon McKitrick via Emacs development discussions.
2024-08-22  4:02                             ` 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=87seuxdb40.fsf@gmail.com \
    --to=eller.helmut@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --cc=jcm@SDF.ORG \
    --cc=pipcet@protonmail.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).